Airbyte - Notice history

Data Sync - Operational

100% - uptime
Feb 2024 · 99.98%Mar · 99.81%Apr · 99.94%
Feb 2024
Mar 2024
Apr 2024

WebApp - Operational

100% - uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 99.87%
Feb 2024
Mar 2024
Apr 2024

Notifications - Operational

100% - uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2024
Mar 2024
Apr 2024

Normalization - Operational

100% - uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2024
Mar 2024
Apr 2024

Airbyte Homepage (Airbyte.com) - Operational

100% - uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2024
Mar 2024
Apr 2024

Third Party Component - Operational

Airbyte API - Operational

100% - uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 100.0%
Feb 2024
Mar 2024
Apr 2024

Connector Builder - Operational

Notice history

Apr 2024

Source Linkedin - Array field as source-defined primary key issue with Destination BigQuery.
  • Resolved
    Resolved

    This incident has been resolved. All impacted users should now be able to update source schema to use a healthy Primary Key and return syncs to a healthy state.

  • Identified
    Identified

    We are continuing to see issues while processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. This fix is a breaking change and will require a reset on your connection. More information here.

  • Identified
    Identified

    There are issues with processing complex primary keys(array/JSON type) that are output by Linked In Ads for users syncing to destination BigQuery. We are continuing to work on a fix for this incident.

  • Investigating
    Investigating
    We are currently investigating this incident.

Mar 2024

Feb 2024

Source Google Ads: replication failure on the user_interest stream
  • Resolved
    Resolved

    This incident is resolved with a workaround.

    After monitoring the workaround we have seen connections return to normal. Once the API issue is resolved from Google we will update to connector to include the data from the USER_INTEREST table.

  • Monitoring
    Monitoring

    We have implemented a workaround to allow connections with the user_interests stream enabled to succeed. The user_interest stream will show null tables while the API is experiencing this outage. We will continue monitoring Googles API status.

  • Identified
    Identified

    We notice wide spread sync failure on the replication of the user_interest stream of the Google Ads source connector. Other streams are correctly replicated at the moment.

    Google Ads API returns 500 HTTP error codes which characterizes a problem in the availability of their service.

    No incident is yet declared on Google Ads status page
    We will reach out to Google Ads support.

Feb 2024 to Apr 2024

Next