Airbyte - Notice history

All systems operational

Data Sync - Operational

99% - uptime
Mar 2024 · 99.82%Apr · 99.94%May · 98.29%

Previous page

Next page

Mar 2024
Apr 2024
May 2024

WebApp - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Notifications - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Normalization - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Airbyte Homepage (Airbyte.com) - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Third Party Component - Operational

Airbyte API - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Connector Builder - Operational

Embedded - Operational

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

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Notice history

May 2024

Airbyte Cloud Inaccessible with Ad Blocking Browser Extensions Enabled
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    A fix has been implemented and we are currently monitoring the update.

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

  • Investigating
    Investigating

    We are currently investigating an issue where Airbyte Cloud is inaccessible if your browser has an ad blocking extension enabled. Disabling the extension should allow you to access your workspace.

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

Source: Facebook Marketing - nonexisting fields error
  • Resolved
    Resolved

    This incident has been resolved.

    As a reminder, this fix is a breaking change. This requires an upgrade to the new 3.1.0 version of Facebook Marketing. Please follow the steps here to successfully update the connector.

  • Monitoring
    Monitoring

    The team has provided a fix which is a breaking change. This requires an upgrade to the new version 3.1.0 of Facebook Marketing. Please follow the steps here to successfully update the connector.

  • Identified
    Identified

    We are continuing to work on a fix for this incident. Meta Appears to have silently modified the schema of the AdsInsights endpoint for conversion_lead_rate and cost_per_conversion_lead  causing the following error message:

    "error": {
        "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)",
  • Investigating
    Investigating

    We are currently investigating this incident. Meta Appears to have silently modified the schema of the AdsInsights endpoint for conversion_lead_rate and cost_per_conversion_lead  causing the following error message:

    "error": {
        "message": "(#100) Tried accessing nonexisting field (cost_per_conversion_lead) on node type (AdsInsights)",
Secrets disabled for some users
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    We have been informed that this issue is impacting additional users. Our team is actively working on a solution to mitigate the problem.

  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

    We are seeing some users connections fail due to their secrets being disabled. The team is aware of this and is currently working on enabling those secrets for the affected users.

Data Sync: Long Running Syncs
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    Some syncs are failing and blocking for many hours before timing out.

Destination: Redshift - Long Running Syncs after Amazon Redshift Updated to version 1.0.67305
  • Resolved
    Resolved

    This incident has been resolved. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. If your connection was actively running a sync before 4:00 PM ET/1:00 PM PT, please cancel the sync and start a new one.

  • Identified
    Identified

    We have identified the root cause of this issue and are actively investigating the fix. This issue is impacting Users who have updated their Redshift to version 1.0.67305 (https://docs.aws.amazon.com/redshift/latest/mgmt/cluster-versions.html#cluster-version-181)

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.
Connector Builder Server Errors
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Update
    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
    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update
    We implemented a fix and are currently monitoring the result.
  • Monitoring
    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.

Mar 2024

Connector Builder Server Errors
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

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

Increase in Sync Failures
  • Resolved
    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
    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
  • Resolved
    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
    Monitoring

    We implemented a fix and are currently monitoring the result.

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

  • Investigating
    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    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
  • Resolved
    Resolved

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

  • Monitoring
    Monitoring

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

  • Update
    Update

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

  • Identified
    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.

Mar 2024 to May 2024

Next