Fivetran Status

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.

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.

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary 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.

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.

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully. Incident Summary 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.

This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connectors are syncing successfully. Incident Summary Description: We identified an issue with the Impact Brand connections, which resulted in syncs failing with 500 Internal Server Errors on the following reporting endpoints:performance_by_partner, performance_by_day, adv_performance_by_ad_media_date Timeline: This issue began on 2026-06-07 at 05:16:55 UTC and was resolved on 2026-06-07 at 19:00:55 UTC. Cause: The failure was caused by a server-side issue on the Impact source. Resolution: We have implemented a fix to temporarily skip the affected endpoints, helping prevent sync failures until the underlying issue is resolved on the Impact side.

This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue where Shopify connections were failing with an HTTP 404 Not Found error. Timeline: The issue began on 2026-06-03 at 13:10 UTC and was resolved on 2026-06-03 at 15:00 UTC. Cause: The failures were caused by an issue on Shopify's side, which resulted in unexpected API error responses. For more information, please refer to the Shopify Status Page: https://www.shopifystatus.com/incidents/gbqcx5fk01gz Resolution: No action was required from our side. The issue was resolved by Shopify, and affected syncs recovered automatically once the upstream issue was addressed.

This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for Hybrid Deployment Agents which resulted in syncs failing with a “Connection pool shut down" error. Timeline: This issue began on May 29, 2026 at 14:10 UTC UTC and was resolved on May 29, 2026 at 23:36 UTC. Cause: A software update introduced a defect in the way Hybrid Deployment Agents managed connections to the underlying container runtime (specifically Docker or Podman). Under certain conditions, the HD Agent attempted to replace an invalid connection, but some internal components continued using references to the original closed connection. This prevented affected agents from starting new sync jobs. Resolution: Fivetran reverted the software change that introduced the issue, deployed a corrected agent version, and remotely updated all affected agents. Following the update, normal sync operations resumed without requiring customer intervention.

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 with Google Display & Video 360 connections, which resulted in syncs failing with an "HTTP 502 Bad Gateway" error. Timeline: This issue began on 2026-05-25 14:56 UTC and was resolved on 2026-05-26 at 04:38 UTC. Cause: The failures were caused by a third-party API side, resulting in HTTP 502 Bad Gateway error responses. There was no Incident reported by Google related to this service on their status page: https://ads.google.com/status/publisher/. Resolution: No action was taken from our end. The issue was resolved on the third-party side, and syncs recovered automatically.

This incident has been resolved. Incident Summary Issue: Fivetran: Multiple connection syncs were failing with an Internal: Failed to read token error. Timeline: This issue began on May 22, 2026, at 02:47 UTC and was resolved on May 22, 2026, at 02:55 UTC. Root Cause: Calls to Firestore (a GCP service) failed due to transient network errors. Resolution: The transient issue affecting Firestore services has stabilised, and all affected Fivetran syncs have recovered and are operating normally.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.