LinkedIn Ads experiencing partial outage

Data Sync

98.24% uptime
Mar 2023 · 99.96%Apr · 99.46%May · 95.41%
Mar 202399.96% uptime
Apr 202399.46% uptime
May 202395.41% uptime

WebApp

99.76% uptime
Mar 2023 · 99.97%Apr · 99.92%May · 99.41%
Mar 202399.97% uptime
Apr 202399.92% uptime
May 202399.41% uptime

Notifications

100.0% uptime
Mar 2023 · 100.0%Apr · 100.0%May · 100.0%
Mar 2023100.0% uptime
Apr 2023100.0% uptime
May 2023100.0% uptime

Normalization

100.0% uptime
Mar 2023 · 100.0%Apr · 100.0%May · 100.0%
Mar 2023100.0% uptime
Apr 2023100.0% uptime
May 2023100.0% uptime

Airbyte Homepage (Airbyte.com)

100.0% uptime
Mar 2023 · 100.0%Apr · 100.0%May · 100.0%
Mar 2023100.0% uptime
Apr 2023100.0% uptime
May 2023100.0% uptime

Third Party Component

Operational

Airbyte API

100.0% uptime
Mar 2023 · 100.0%Apr · 100.0%May · 100.0%
Mar 2023100.0% uptime
Apr 2023100.0% uptime
May 2023100.0% uptime

Connector Builder

Operational

Notice history

May 2023

Long running syncs
  • Resolved
    Resolved

    After monitoring the fix implemented we have resolved the issue.

    The issue occurred under certain conditions and caused syncs to to not be properly retried.

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

  • Monitoring
    Monitoring

    We believe we have found the root cause and have implemented a fix. We will be monitoring the results.

  • Investigating
    Investigating

    We are still seeing instances of these long running syncs and failures with "Setting attempt to FAILED because the temporal workflow for this connection was restarted, and existing job state was cleaned.". We are continuing our investigation and will add updates as we have them.

  • Monitoring
    Update

    We have been monitoring the results over the weekend and would like to continue monitoring throughout the day.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. Any sync affected will show as a failed sync but the next scheduled sync should run as expected.

  • Identified
    Identified

    We have identified an issue that is causing syncs to run longer than expected. We are taking action to address these long running syncs.

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

Apr 2023

Sync Failures in EU region
  • Resolved
    Resolved

    This issue has been resolved. If your most recent sync failed, we expect the next sync to succeed.

    We apologize for the inconvenience and thank you for your patience as the team worked to resolve the issue.

  • Monitoring
    Monitoring

    We have updated our networking stack to workaround the flooded Paris GCP datacenter. Our EU syncs can now pull secrets from a healthy datacenter which should fix the issue with our EU syncs. We have verified that EU syncs are currently working. If you had a failed sync starting it again now should work. We are continuing to monitor the incident.

  • Identified
    Update

    We are continuing to work on a fix for this incident.

  • Identified
    Identified

    We have identified the root cause and are working on the resolution.

    GCP’s Secret manager service powers part of the Airbyte EU Sync infrastructure. Because of the flooding in GCP’s Paris datacenter Airbyte’s EU Sync’s are unable to start.

    We are working on resolving those secrets from a functioning GCP EU region. Until we can set up that system syncs may be run successfully from the US for any customers not bound by GDPR.

  • Investigating
    Investigating

    Many syncs in the EU region are currently failing. They appear to be impacted by a general GCP outage in the Paris region https://status.cloud.google.com/incidents/dS9ps52MUnxQfyDGPfkY#73mBtVKKfeJGJ1yaY7hV

    We are currently monitoring the situation.

Mar 2023

Airtable source: Revoked third-party integration access.
  • Resolved
    Resolved

    A fix has been pushed.

    If your connection has been failing with '400 Client Error: Bad Request for url: https://airtable.com/oauth2/v1/token' permissions error, please re-authenticate one last time.

    We apologize for this inconvenience and thank you for your patience while worked to resolve the issue.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are still continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent fix for this incident.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a fix for this incident.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are still continuing to work on a permanent solution for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    The team is continuing their work on a permanent fix for the Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work on a permanent fix for Airtable source authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continually working on a permanent solution for Airtable authentication.

    As a temporary workaround: please re-authenticate your Airtable connector and run your sync.

  • Identified
    Update

    We are continuing to work with Airtable to sort out the authentication for our integration.

    As a temporary workaround: You can re-authenticate your Airtbale connector and run a sync.

  • Identified
    Update

    We are still trying to work with Airtable to sort out why our integration authentication was revoked and reestablish the integration.

    The current workaround is still to re-authenticate and to rerun your sync.

    We apologize for the inconvenience and hope to have this issue resolved soon.

  • Identified
    Identified

    We are seeing a number of failures for Airtable source connections due to Airtable revoking Airbyte as a third-party integration.

    The following error will be seen in the Airbyte UI:
    2023-03-27 07:58:17 - Additional Failure Information: '400 Client Error: Bad Request for url: https://airtable.com/oauth2/v1/token'

    You can reauthenticate and run a sync for a temporary fix.

    We currently working on a fix for this incident.

Mar 2023 to May 2023