Airbyte - Notice history

All systems operational

Data Sync - Operational

99.91% uptime
Feb 2024 · 99.98%Mar · 99.81%Apr · 99.94%

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

WebApp - Operational

99.96% uptime
Feb 2024 · 100.0%Mar · 100.0%Apr · 99.87%

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Notifications - Operational

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

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Normalization - Operational

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

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Airbyte Homepage (Airbyte.com) - Operational

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

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Third Party Component - Operational

Airbyte API - Operational

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

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Connector Builder - Operational

Airbyte Agents - Operational

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

Previous page

Next page

Feb 2024
Mar 2024
Apr 2024

Notice history

View current status

Apr 2024

Source Linkedin - Array field as source-defined primary key issue with Destination BigQuery.
Resolved289 hours 30 minutes
  • Resolved
    UTC
    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
    UTC
    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
    UTC
    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
    UTC
    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
    UTC
    Investigating
    We are currently investigating this incident.
Connector Builder Server Errors
Resolved13 hours 25 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Update
    UTC
    Update

    We are still investigating an issue that is currently affecting the connector builder. Thank you for your patience as we dig into the issue.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue that is currently affecting the connector builder. Thank you for your patience as we dig into the issue.

cloud.airbyte.com/workspaces Not Loading
ResolvedPartial outage1 hour 56 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    We are currently investigating this incident. Users should still be able to load individual workspace pages but the list of workspace page is inaccessible.

Airbyte Cloud is Down
ResolvedMajor outage1 hour 57 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Update
    UTC
    Update
    We implemented a fix and are currently monitoring the result.
  • Monitoring
    UTC
    Monitoring

    We are currently investigating this incident. You may not be able to access your workspace at this time. Some jobs may be affected.

Stuck Syncs
ResolvedPartial outage1 hour 57 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Mar 2024

Connector Builder Server Errors
ResolvedPartial outage2 hours 42 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Investigating
    UTC
    Investigating

    We are currently investigating this incident. The Connector Builder is currently returning 502 Server Errors and is inaccessible.

Increase in Sync Failures
ResolvedDegraded performance2 hours 43 minutes
  • Resolved
    UTC
    Resolved

    We implemented a fix and this issue has been successfully resolved.

    Syncs should now be starting and running normally. If your most recent sync failed, your next scheduled sync should succeed.

    Thank you for your patience as we investigated this issue and we apologize for any inconvenience.

  • Identified
    UTC
    Identified

    We have seen an elevated number of sync failures with the following error messages:

    server 502 error message or Client error : 409 {"message":"Non-terminal Workload with mutexKey

    Our team is working on a fix and we apologize for any inconvenience caused and appreciate your patience as we work to resolve this issue.

EU Sync Failures
ResolvedPartial outage40 minutes
  • Resolved
    UTC
    Resolved

    The issue has been successfully resolved. Thank you again for your patience as worked this issue to resolution and we apologize for any inconvenience this issue might have caused.

  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are currently monitoring the result.

    Thank you for your patience as we work to resolve this issue.

  • Investigating
    UTC
    Investigating

    We are currently investigating an issue that is currently causing an increase in sync failures. Thank you for your patience as we investigate this issue.

EU Syncs Failing
ResolvedPartial outage1 hour 30 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    A thread leak caused a pod to fail, leading to a subset of syncs in the EU data plane to fail.

Syncs failing in `gcp-us-west3-0` due to job pods not updating their output
Resolved3 hours 24 minutes
  • Resolved
    UTC
    Resolved

    The team has monitored the gcp-us-west3-0 data plane and has determined the issue has been resolved.

  • Monitoring
    UTC
    Monitoring

    The team has provided a fix and reenabled the affected data plane and is currently monitoring the situation.

  • Update
    UTC
    Update

    We have a workaround allowing new jobs succeed. We are working on a fix for gcp-us-west3-0 dataplane

  • Identified
    UTC
    Identified

    We are having an internal issue where our job pods cannot write their output in `gcp-us-west3-0` dataplane. As a result, syncs are failing. The team is currently working on a fix.

Feb 2024

EU syncs are delayed
ResolvedDegraded performance1 hour 47 minutes
  • Resolved
    UTC
    Resolved

    This incident is resolved. EU syncs are operational

  • Monitoring
    UTC
    Monitoring

    We have identified an issue that prevents sync in the European data plane from running. A fix has been deployed, and we are monitoring.

Blocked syncs in EU
ResolvedPartial outage29 minutes
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Investigating
    UTC
    Investigating

    We are currently investigating an issue that is currently affecting syncs running in EU data residency. Thank you for your patience as we dig into the issue.

Job Failures
Resolved
  • Resolved
    UTC
    Resolved

    Elevated job error rates from 4pm - 4:10pm.

Source Google Ads: replication failure on the user_interest stream
ResolvedDegraded performance185 hours 43 minutes
  • Resolved
    UTC
    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
    UTC
    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
    UTC
    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.

Previous

Feb 2024 to Apr 2024

Next