Airbyte - Notice history

All systems operational

Data Sync - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 99.98%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

WebApp - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Notifications - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Normalization - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Airbyte Homepage (Airbyte.com) - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Third Party Component - Operational

Airbyte API - Operational

100% - uptime
Apr 2025 · 100.0%May · 100.0%Jun · 99.98%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Connector Builder - Operational

Notice history

Jun 2025

Connector Creation, Updates, and Checks Failing with 403 Errors
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    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
  • Resolved
    Resolved

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

  • Monitoring
    Monitoring

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

  • Identified
    Identified

    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.

  • Investigating
    Investigating

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

    Some users reported the inability to access their Airbyte Cloud workspaces, purportedly related to the ongoing GCP outage: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

BigQuery Destination Connections failing due to Google Cloud Outage
BigQuery - Error message: Input was fully read, but some streams did not receive a terminal stream status message.
  • Resolved
    Resolved

    We have confirmed that the revert has returned impacted connections to a healthy state.

  • Monitoring
    Monitoring

    We have reverted the code change that caused this error and are in the process of creating a more permanent fix.

  • Identified
    Identified

    We have identified the component that caused this error. The team is in the process of reverting the change which should restore all impacted connections to a healthy state.

  • Investigating
    Investigating
    We are currently investigating this incident.

May 2025

Issues with Custom Stream Prefixes and Namespaces
  • Resolved
    Resolved

    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

  • Monitoring
    Monitoring

    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.

  • Identified
    Identified

    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.

  • Investigating
    Investigating

    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
  • 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.
Heartbeat time out issues.
  • Resolved
    Resolved

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

  • Monitoring
    Monitoring

    • We identified the issue and deployed a fix.

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

Maintenance Window
  • Completed
    May 01, 2025 at 3:00 PM
    Completed
    May 01, 2025 at 3:00 PM
    Maintenance has completed successfully
  • In progress
    May 01, 2025 at 1:00 PM
    In progress
    May 01, 2025 at 1:00 PM
    Maintenance is now in progress
  • Planned
    May 01, 2025 at 1:00 PM
    Planned
    May 01, 2025 at 1:00 PM
    We are planning for a scheduled maintenance during that time.

Apr 2025

Error Updating Destination Connectors
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    Existing Destination Connectors are currently unable to have updates applied. The team is actively investigating the root cause of this.

Source Facebook Marketing Insights Streams - Error: `string indices must be integers, not 'str'`
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Previously failing connections have begun succeeding once again, indicating that the issue has been fixed in the Meta API.

  • Investigating
    Investigating

    We are currently investigating this incident and believe it is due to an outage within the Meta API.

Apr 2025 to Jun 2025

Next