Fivetran Status Page

Jun 19, 2026 · resolved Jun 19

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue in which Apple Search Ads connections were failing with the error "HTTP 400 Bad Request." Timeline: This issue began on June 18, 2026, at 17:47 UTC and was resolved on June 19, 2026, at 11:02 UTC. Cause: The issue was caused by a recent code change that introduced an unexpected error in Apple Search Ads connection processing. Resolution: Identified the problematic change and reverted it Following the change, affected Apple Search Ads connections resumed normal operation and the issue was fully resolved.

Jun 17, 2026 · resolved Jun 17

Incident Summary Description: We identified an issue where Hybrid Deployment connections were failing with a "Failed to generate data key for HD encryption context" or "Failed to receive message length" exception. Timeline: This issue began on June 17, 2026, at 08:10 UTC and was resolved on June 17, 2026, at 15:50 UTC. Cause: A recent code change introduced an issue affecting Hybrid Deployment connectors, specifically Oracle HVA and SQL Server HVA connectors. As a result, sync jobs for impacted connectors would start and then fail. Resolution: We reverted the problematic change and deployed a hotfix. After the fix was deployed, affected connectors began recovering and syncs started succeeding again.

Jun 14, 2026 · resolved Jun 14

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue for Customer.io, which resulted in syncs failing with a 502 HTTP error. Timeline: This issue began on 2026-06-13 20:26 UTC and was resolved on 2026-06-14 14:52 UTC. Cause: The issue was caused by intermittent upstream API failures on the Customer.io side. The root-cause behaviour fluctuated throughout the incident, shifting between generic server errors across multiple endpoints. Resolution: Fivetran implemented a skip-on-failure mechanism to bypass 502 HTTP errors and allow syncs to proceed. A permanent root-cause fix will be deployed by Customer.io.

Jun 8, 2026 · resolved Jun 8

Description: We identified an issue affecting manual and API-triggered connection syncs, causing syncs to fail to start and return API errors. Timeline: This issue began on June 8, 2026, at 22:00 UTC and was resolved on June 8, 2026, at 22:35 UTC. Cause: The elevated API error count was caused by an incident with a third-party service used to orchestrate sync execution. As a result, requests to trigger connection syncs through both the API and the Fivetran dashboard were intermittently unsuccessful. Reference: https://status.temporal.io/incidents/8msytm7vpfbv Resolution: The third-party service provider resolved the underlying issue, restoring normal functionality. Following confirmation that sync triggering was operating as expected, the incident was closed. Customers can now successfully trigger syncs through both the API and the dashboard.

Jun 7, 2026 · resolved Jun 7

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue with the Microsoft Advertising connections, which resulted in syncs failing with a "Report processing failed: (StreamProcessing)" error. Timeline: This issue began on June 7, 2026, at 05:00 UTC and was resolved on June 7, 2026, at 13:00 UTC. Cause: The connectors that were syncing Geographic Performance report tables in Microsoft Ads started failing consistently due to an issue with the Microsoft Ads API on Microsoft's end. Resolution: This has been automatically resolved on the Microsoft Ads API affecting the GeographicPerformanceReport, and the connectors are succeeding now.