Fivetran Outage History

Multiple QuickBooks connections in Fivetran failed to sync due to a scheduled maintenance window on the QuickBooks side that occurred on April 25, 2026, from 9:00 PM to 11:30 PM PT. The sync failures were automatically resolved once the QuickBooks maintenance window completed, with the incident lasting approximately 6 minutes from identification to resolution.

Multiple Fivetran Twitter Ads connectors failed for 14.6 hours due to the Twitter Ads API returning persistent HTTP 500 server errors on reporting endpoints. Fivetran deployed a fix that enables connectors to gracefully handle these API errors by skipping affected accounts with dashboard warnings while preserving sync progress for successful accounts. Skipped data will be automatically retried on the next sync cycle.

Fivetran experienced sync start delays for 4.3 hours due to an Azure outage in the East-US-2 region that affected General Services. The incident impacted pod scaling functionality and created a backlog of syncs that needed to be processed. The issue was resolved after Azure completed their fix rollout, allowing syncs to return to normal operation.

Fivetran experienced sync failures affecting their General Services starting at 8AM Pacific time. The issue was identified and a fix was implemented, with sync failure rates returning to normal levels within approximately 2 hours. The incident was fully resolved after 2.4 hours of monitoring to ensure stability.

Multiple Twitter Ads connections in Fivetran experienced sync failures due to access level and permission errors (Code 453) for 5.5 hours. The issue affected the Twitter Ads component, preventing data synchronization for affected connections. Fivetran identified the root cause, implemented a fix, and resolved the incident after monitoring the results.

Fivetran experienced sync failures across multiple Twitter Ads connections due to access level and permission errors (Code 453). The issue affected all Twitter Ads integrations for 17 minutes. The problem was identified and resolved by the engineering team.

Fivetran's Apple App Store connectors experienced sync failures with "Reporter is currently unavailable" errors due to an intermittent issue on Apple's third-party service side. The incident affected Apple App Store data connections for approximately 8 hours from April 20th at 17:15 UTC to April 21st at 01:20 UTC. The issue was automatically resolved by the third-party service without requiring intervention from Fivetran.

Fivetran's Twitter Ads connections experienced sync failures for 7.4 hours due to the Twitter API returning null values in a primary key field, causing "Null primary key found" errors. The issue was resolved through a combination of Twitter fixing their API outage and Fivetran deploying a hotfix to skip rows with missing primary keys. All affected connectors returned to normal syncing operations.

Fivetran's Twitter Ads connectors experienced sync failures for 3.9 hours due to a third-party authentication error (code 215) from Twitter's API when fetching async job results. The issue was caused by Twitter's API returning "Bad Authentication data" errors on their side. Fivetran resolved the problem by implementing a workaround that skips the problematic endpoints for affected accounts, restoring normal connector functionality.

Fivetran's Twitter Ads and Twitter Organic connections experienced sync failures for 2.9 hours due to Twitter's API returning HTTP 500 internal server errors when attempting to fetch reports. The issue was caused by a third-party error on Twitter's side that resulted in "URI is not absolute" failures. Fivetran resolved the incident by implementing a workaround that skips reports for problematic accounts, allowing connectors to return to normal operation.