Airbyte had 26 outages in the last 2 years totaling 10h 27m of downtime — averaging 1.1 incidents per month.
There were 26 Airbyte outages since June 25, 2025 totaling 10h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this incident.
We are continuing to work on a fix for this incident.
$13
Type: Incident Affected Components: Amazon Seller Partner Jun 9, 00:00:00 GMT+0 - Resolved - We identified an issue causing Amazon Seller Partner connections to fail with the error: `Config validation error: None is not of type 'string'` Jun 9, 09:00:00 GMT+0 - Resolved - This incident has been resolved. Any connections that failed due to this error should be re-synced and are expected to complete successfully.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are currently investigating this incident.
This incident has been resolved.
We are continuing to work on a fix for this incident.
This incident has been resolved.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Airbyte Agents are unresponsive. The Airbyte Agent SDK and MCP are still working as expected. We are currently investigating this incident.
This incident has been resolved.
Type: Incident Duration: 5 hours and 40 minutes Affected Components: Shopify Source, Third Party Component Apr 16, 08:30:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 16, 09:00:00 GMT+0 - Identified - Syncs using the `order_agreements` stream in the Shopify source connector are failing with the error: ``` The parent 'node' field for a nested connection must return a type that implements the 'Node' interface. ``` This is caused by a change on Shopify's side to their Bulk Operations API validation. The stricter validation now rejects bulk queries where nested connections use types that don't implement the `Node` interface — the `agreements` connection falls into this category Apr 16, 14:10:15 GMT+0 - Monitoring - Shopify has implemented a fix and are currently monitoring the result. Apr 16, 14:10:26 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 5 hours and 26 minutes Affected Components: MongoDB Source Mar 20, 09:30:10 GMT+0 - Investigating - We are currently investigating this incident. Mar 20, 10:40:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 20, 13:16:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 20, 14:55:43 GMT+0 - Resolved - This incident has been resolved. Thank you for your patience as we worked this issue to resolution and we apologize for any inconvenience this issue might have caused.
Type: Incident Duration: 2 hours and 28 minutes Affected Components: Airbyte API, Agent Engine, Data Sync, WebApp Mar 10, 21:00:00 GMT+0 - Investigating - We observed elevated database load which caused slower sync performance and intermittent UI delays for some users. Our team is investigating. We are currently investigating this incident. Mar 10, 23:00:00 GMT+0 - Resolved - The issue has been resolved and performance has returned to normal. Users who experienced slow or failed syncs during this time can retry their syncs.
Type: Incident Duration: 4 hours and 10 minutes Affected Components: Snowflake Destination, Snowflake Source Dec 16, 17:04:00 GMT+0 - Resolved - Snowflake has resolved their outage. Dec 16, 12:54:20 GMT+0 - Investigating - We are aware of an ongoing incident affecting Snowflake, which may impact Airbyte connections that use Snowflake as a destination or source. Some users may experience failed syncs, increased latency, or intermittent errors while the Snowflake incident is ongoing. Our systems are otherwise operating normally, and we are actively monitoring the situation.
Type: Incident Duration: 24 days, 17 hours and 38 minutes Oct 30, 04:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 30, 13:53:37 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 3 hours and 43 minutes Affected Components: Data Sync Oct 24, 16:05:00 GMT+0 - Identified - We noticed an issue with delays during the `check`, `discover`, and `replicate` operations causing syncs to run slowly. Oct 24, 19:48:00 GMT+0 - Resolved - This incident has been resolved. Impacted syncs should return to a healthy state on the next sync job. Oct 24, 18:48:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 7 hours and 30 minutes Affected Components: WebApp Oct 20, 19:00:15 GMT+0 - Investigating - We are currently investigating this incident and believe it to be related to the AWS Outage. Oct 21, 02:30:00 GMT+0 - Resolved - This incident has been resolved. Oct 20, 19:53:15 GMT+0 - Monitoring - This incident appears to be related to the AWS Outage and we are monitoring the situation.
Type: Incident Duration: 6 hours and 23 minutes Affected Components: Airbyte Homepage (Airbyte.com) Oct 20, 11:30:00 GMT+0 - Investigating - [Airbyte.com](http://Airbyte.com) is not loading due to the AWS outage Oct 20, 16:03:24 GMT+0 - Monitoring - [Airbyte.com](http://Airbyte.com) is not loading due to the AWS outage and we are monitoring the situation. Oct 20, 17:52:56 GMT+0 - Resolved - [**Airbyte.com**](http://Airbyte.com) is now loading!
Type: Incident Duration: 1 day, 1 hour and 22 minutes Affected Components: HubSpot Source Connector Oct 16, 09:37:57 GMT+0 - Investigating - We are currently investigating this incident. Oct 16, 12:42:39 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 17, 10:59:50 GMT+0 - Resolved - This incident has been resolved. Affected users who experienced missing or null data will need to run a new sync for the data to populate in their destination. A full refresh is not required.
Type: Incident Duration: 1 hour and 25 minutes Affected Components: Data Sync Sep 25, 00:19:54 GMT+0 - Investigating - We are currently investigating this incident. Sep 25, 01:06:19 GMT+0 - Monitoring - We identified the issue was caused by a Docker Hub outage. We are currently observing recovery and are actively monitoring. Sep 25, 01:45:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 51 minutes Affected Components: Agent Engine Sep 17, 21:38:28 GMT+0 - Investigating - We are currently investigating this incident. Sep 17, 22:29:44 GMT+0 - Resolved - Issue has been resolved
Type: Incident Duration: 2 minutes Affected Components: WebApp Aug 19, 18:27:07 GMT+0 - Investigating - We are currently investigating this incident. Aug 19, 18:29:14 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 5 days, 1 hour and 20 minutes Affected Components: Monday Source Aug 6, 12:30:00 GMT+0 - Identified - The Monday API made an unexpected change in a recent update initiating this error. \[See Monday Community thread HERE.\](https://community.monday.com/t/anyone-else-400-invalid-graphql-request-error-from-api-with-make-monday-modules/118566/4) Aug 11, 13:40:52 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 11, 13:50:00 GMT+0 - Resolved - This incident has been resolved. All previously impacted connections should now be succeeding on the newest version of the Source Monday Connector.
Type: Incident Duration: 56 minutes Affected Components: Data Sync, WebApp Jul 28, 23:06:28 GMT+0 - Investigating - We are currently investigating this incident. Jul 28, 23:25:11 GMT+0 - 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. Jul 29, 00:02:26 GMT+0 - Resolved - This incident has been resolved, all monitors are indicating load times have returned to normal.
Type: Incident Duration: 5 hours and 29 minutes Affected Components: Data Sync, WebApp Jul 17, 13:15:55 GMT+0 - Investigating - We are currently investigating this incident. Jul 17, 16:15:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jul 17, 18:37:24 GMT+0 - Monitoring - 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. Jul 17, 18:45:00 GMT+0 - Resolved - This incident has been resolved. The WebApp and all Connections have returned to performing as expected.
Type: Incident Duration: 20 hours and 57 minutes Jul 16, 14:02:03 GMT+0 - Investigating - We are currently investigating this incident. Jul 16, 14:46:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 17, 10:58:42 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 3 hours and 10 minutes Jul 10, 09:49:37 GMT+0 - Monitoring - We are currently investigating this incident related to updating connection settings Jul 10, 13:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 8 hours and 45 minutes Affected Components: Google Ads Source Jul 3, 03:30:00 GMT+0 - Resolved - Google has resolved their outage: Impacted connections should return to a healthy state. Jul 2, 18:45:00 GMT+0 - Identified - 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: