Fivetran Outage History

Fivetran's Shopify connections experienced failures with HTTP 404 errors due to an outage on Shopify's side that caused their API endpoints to return unexpected error responses. The issue affected all Shopify connector syncs for 1.9 hours on June 3rd, 2026. The problem was resolved automatically when Shopify fixed their upstream issue, with no action required from Fivetran.

Fivetran's Hybrid Deployment Agent experienced a "Connection pool shut down" error that caused syncs to fail to start and connections to fail during setup tests, affecting only Docker/Podman environments. The issue lasted 7.4 hours and impacted data synchronization operations for customers using hybrid deployments. Fivetran resolved the incident by deploying a hot fix and releasing updated HD agent images, with existing customers advised to restart their controllers to apply the fix.

Fivetran's Google Display & Video 360 connections experienced sync failures due to "HTTP 502 Bad Gateway" errors caused by issues on Google's third-party API side. The incident lasted 6.5 hours and affected data synchronization for users of this specific connector. The issue resolved automatically when Google fixed their API problems, with no action required from Fivetran's side.

Multiple Fivetran connection syncs failed with "Internal: Failed to read token" errors due to transient network issues affecting Google Cloud Platform's Firestore service. The incident impacted General Services and lasted 14 minutes from 02:47 to 05:16 UTC on May 22, 2026. The issue was resolved when the Firestore network problems stabilized, allowing all affected syncs to recover and return to normal operation.

Fivetran experienced a 2.2-hour delay in delivering user-facing logs and external logs due to a service misconfiguration. The issue affected General Services and was resolved by disabling the problematic component. Log processing delays returned to normal levels after the fix was implemented and monitored.

Multiple Salesforce connections in Fivetran experienced sync failures with HTTP 503 Service Unavailable errors due to a source-side outage in the Salesforce API that caused 500 Internal Server Error responses. The incident lasted 3.8 hours from May 21, 2026 at 20:00 UTC to May 22, 2026 at 00:30 UTC and resolved automatically when Salesforce fixed the issue on their end, with syncs returning to normal operation.

Fivetran's Qualtrics connector experienced intermittent sync failures for 8.3 hours due to HTTP 400 Bad Request errors on the TransactionBatches endpoint, caused by a third-party issue. The incident affected Qualtrics data synchronization services. Fivetran implemented a fix and resolved the issue after coordinating with third-party support and exploring workarounds.

Fivetran's Twitter Ads connections experienced failures due to BadRequestException errors caused by changes on Twitter's side. The issue affected all Twitter Ads data syncing for 3.8 hours. Fivetran identified the problem, implemented a fix, and resolved the incident after monitoring confirmed the solution was working.

Fivetran experienced intermittent connection sync failures with "Token not found" errors for 28 minutes due to an internal network disruption in the scheduling layer. The network issues caused cascading failures across dependent connection services, affecting customers' data synchronization processes. All services returned to normal operation once network connectivity was restored.

Fivetran experienced sync failures for Amazon Ads connections due to a NullPointerException caused by a recent Operations Consolidation change that introduced a regression. The issue lasted 1.6 hours and was resolved by reverting the problematic change, after which affected connections resumed syncing successfully with success rates returning to normal levels.