Fivetran Outage History

Facebook Pages connectors experienced sync failures for 4.4 hours due to instability in newly introduced monetization metrics, causing "An unknown error has occurred" messages when fetching data from Facebook's API. Fivetran resolved the issue by disabling monetization metrics processing for the Facebook Pages connector, allowing affected syncs to resume normal functionality.

Fivetran's Apple App Store connections experienced sync failures for 3.3 hours due to Apple's third-party /v1/financeReports endpoint returning "Reporter is currently unavailable" errors (HTTP 503). The issue was automatically resolved from Apple's side without requiring intervention from Fivetran, and all affected connections returned to normal sync operations.

Fivetran experienced a delay in notifications and alerts on their dashboard for 26 minutes due to a recent code change. The issue affected general services and prevented users from receiving timely notifications through the dashboard interface. The problem was resolved by reverting the problematic code change.

Fivetran's Typeform connections experienced failures due to changes in the source system's response format for FORM_INSIGHT data, lasting 3.3 hours. The issue was identified as originating from modifications on Typeform's side that caused sync errors. Fivetran implemented a fix and confirmed syncs had recovered after monitoring the results.

Fivetran's Marketo connections experienced sync failures for 2.5 hours due to a "PROGRAM_MEMBERSHIP: fields not specified" error caused by a recent connector change that impacted API requests. The issue was resolved by reverting the problematic change and redeploying the fix, with success rates returning to normal levels.

Fivetran's Talkdesk connections experienced sync failures for 7.4 hours due to "HTTP 404: Report file not found" errors caused by issues with Talkdesk's reporting endpoints in the US region. The problem originated from the third-party Talkdesk service and was resolved through mitigation actions implemented by Talkdesk without requiring any changes from Fivetran. Success rates returned to normal levels and affected connections resumed syncing successfully after the resolution.

Fivetran's Twilio connections experienced sync failures with "504 Gateway Timeout Error" due to degraded performance on Twilio's third-party service. The issue affected Twilio data syncs for approximately 1.4 hours on May 8th, 2026, from 01:20 AM to 02:41 AM UTC. The problem was automatically resolved from Twilio's side without requiring intervention from Fivetran, and all affected connections returned to normal syncing operations.

Fivetran's Amazon Selling Partner connections experienced sync failures with HTTP 500 Internal Server Errors for 6.6 hours due to degraded performance in Amazon's Selling Partner API. The issue was caused by problems on Amazon's third-party service and was automatically resolved without Fivetran intervention once Amazon restored normal API performance.

Fivetran's HubSpot connections experienced sync failures for 2.2 hours due to "HTTP 500 Internal Server Error" responses from HubSpot's event-definitions endpoint, which was caused by a regional AWS outage affecting HubSpot's services. The issue was automatically resolved from HubSpot's side without requiring intervention from Fivetran, and all affected connections returned to normal syncing operations.

Fivetran's Klaviyo connectors experienced sync failures for 4.7 hours due to HTTP 401 unauthorized errors when accessing Klaviyo's Template endpoint, causing reconnect tasks to appear on user dashboards. The issue was resolved by implementing skip logic that disables syncing of the email_template table when the endpoint returns 401 errors, while allowing all other tables to sync normally. All affected connectors have since resumed normal sync functionality.