Airbyte - Notice history

All systems operational

Data Sync - Operational

99.99% uptime
May 2025 · 100.0%Jun · 99.96%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

WebApp - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Notifications - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Normalization - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Airbyte Homepage (Airbyte.com) - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Third Party Component - Operational

Airbyte API - Operational

99.99% uptime
May 2025 · 100.0%Jun · 99.96%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Connector Builder - Operational

Airbyte Agents - Operational

100.0% uptime
May 2025 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2025
Jun 2025
Jul 2025

Notice history

View current status

Jul 2025

Slow Page Loading Times in Cloud UI and Stalled Syncs
ResolvedDegraded performance55 minutes
  • ResolvedUTC
    This incident has been resolved, all monitors are indicating load times have returned to normal.
  • MonitoringUTC
    A fix has been implemented and we are currently monitoring the update. Thank you for your patience as we work to resolve this issue.
  • InvestigatingUTC
    We are currently investigating this incident.
Performance issue: Degraded sync performance - (Error: An internal transient Airbyte error has occurred. The sync should work fine on the next retry)
ResolvedDegraded performance5 hours 29 minutes
  • ResolvedUTC

    This incident has been resolved. The WebApp and all Connections have returned to performing as expected.

  • MonitoringUTC

    We implemented a fix and are currently monitoring the result. All previously stalled syncs should now be progressing once again and interactions with the WebApp have returned to expected responsiveness.

  • IdentifiedUTC
    We are continuing to work on a fix for this incident.
  • InvestigatingUTC
    We are currently investigating this incident.
HTTP 403 - error when trying to log into Airbyte cloud.
ResolvedMajor outage20 hours 56 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC
    We are currently investigating this incident.
Updating connection settings: An unknown error occurred. (HTTP 409)
ResolvedMajor outage3 hours 10 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We are currently investigating this incident related to updating connection settings
Google Ads outage causing connection failures for Source Google Ads
ResolvedMajor outage8 hours 45 minutes
  • ResolvedUTC
    Google has resolved their outage: Impacted connections should return to a healthy state.
  • IdentifiedUTC

    An outage in Google Ads has caused failures for connections with a Google Ads Source connector. Syncs are failing with 503 errors. See Google Ads outage here: https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu

Jun 2025

Facebook Marketing Connector – Syncs Returning Incomplete or No Data
ResolvedPartial outage30 hours 8 minutes
  • ResolvedUTC
    This incident has been resolved.
  • UpdateUTC

    This issue is not caused by Airbyte’s product. It stems from an ongoing incident with Meta’s systems. For the latest updates, please refer to Meta's Marketing API status page.

  • IdentifiedUTC

    This behavior appears to be related to the Facebook API itself. We’ll continue actively monitoring the situation and keep evaluating options as more information becomes available.

  • InvestigatingUTC

    Several workspaces using the Facebook Marketing connector have reported successful syncs returning little or no data, despite ongoing ad activity and no reported changes. The issue appears to impact multiple accounts and is currently under engineering investigation.

Connector Creation, Updates, and Checks Failing with 403 Errors
ResolvedMajor outage16 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

    We’re seeing a platform issue where creating, updating, and running checks on connectors is failing with a 403 error.
    Error:
     Init container error... Client error: 403

    Updates will be posted here as soon as we have them. Thank you!

Google Analytics 4 Connections failing with `time data '' does not match format '%Y-%m-%d'` errors
ResolvedMajor outage15 hours 35 minutes
  • ResolvedUTC

    This incident has been resolved. All impacted syncs have returned to a healthy state.

  • MonitoringUTC

    We have reverted the update that was responsible for the error. All connections impacted should return to a healthy state.

  • IdentifiedUTC

    We have identified the update responsible for this error and are in the process of reverting it. Once reverted, connections should return to a healthy state.

  • InvestigatingUTC

    We have begun seeing failures on Google Analytics 4 connections due to time data '' does not match format '%Y-%m-%d'

Airbyte Cloud WebApp inaccessible for some regions, likely due to GCP Outage
ResolvedPartial outage26 hours 12 minutes
BigQuery Destination Connections failing due to Google Cloud Outage
ResolvedMajor outage27 hours 20 minutes

May 2025

Issues with Custom Stream Prefixes and Namespaces
ResolvedDegraded performance5 hours 30 minutes
  • ResolvedUTC

    This incident has been resolved. All impacted connections have been rolled back and final tables should be restored to a healthy state. If there are any lingering concerns please submit a ticket via https://support.airbyte.com/hc/en-us/requests/new

  • MonitoringUTC

    Connection states for impacted connections have been rolled back to a healthy state prior to the issue. Sync jobs after this time will now sync all data to the proper tables, including the data previously synced to the non-prefixed tables.

    Connections with Source Postgres using CDC will likely need to run a Refresh on the connection to restore it to a healthy state.

  • IdentifiedUTC

    We’ve identified the root cause of the issue and have stopped syncs from writing to incorrect tables. Our team is now actively working to restore the affected data to the correct, prefixed final tables.

  • InvestigatingUTC

    Issues regarding data being written with the expected stream prefixes is actively being investigated.

Hubspot - The main container of the CHECK operation returned an exit code 137
ResolvedDegraded performance78 hours 30 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC
    We are currently investigating this incident.
Heartbeat time out issues.
Resolved2 hours 37 minutes
  • ResolvedUTC

    This incident has been resolved. We are not seeing the error in our monitoring.

  • MonitoringUTC

    • We identified the issue and deployed a fix.

    • We are monitoring the frequency of the error to ensure that it is properly resolved.

MAY1
Maintenance Window
CompletedMaintenance2 hours
  • CompletedMay 01, 2025 at 3:00 PMUTC
    Maintenance has completed successfully
  • In progressMay 01, 2025 at 1:00 PMUTC
    Maintenance is now in progress
  • PlannedMay 01, 2025 at 1:00 PMUTC
    We are planning for a scheduled maintenance during that time.

Previous

May 2025 to Jul 2025

Next