Fivetran Outage History

60 incidents recorded over the last 365 days, 60 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Fivetran status67.32% uptime history

Every Recorded Fivetran Incident

Fivetran incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 10, 20263rd Party: Some Ramp connections failing with 529 response errorsThis incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. <b>Incident Summary</b> Description: We identified an…1h 29mResolved
Jul 7, 20263rd Party: QuickBooks connections failing with “Failed to sync 1 endpoint” errorThis incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue…2h 49mResolved
Jul 6, 20263rd Party: Some AppLovin connectors are failingThis 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 have identified an issue with…2h 36mResolved
Jun 19, 2026Fivetran: Apple Search Ads connections are failing with error "HTTP 400 Bad Request"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…4h 27mResolved
Jun 17, 2026Fivetran: Multiple Hybrid Deployment Connections are failingIncident 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"…5h 26mResolved
Jun 14, 20263rd Party: Multiple Customer.io connections are failing with 5xx errorThis 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…15h 52mResolved
Jun 8, 20263rd Party: Failures Triggering Connection Syncs via API and DashboardDescription: 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…0 minResolved
Jun 7, 20263rd Party: Some Microsoft Advertising connectors are failing with a "Report processing failed: (StreamProcessing)" errorThis 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…5h 17mResolved
Jun 7, 20263rd Party: Some Impact Brand connections are failing with "HTTP 500 Internal server" errorThis 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…1h 18mResolved
Jun 3, 20263rd Party: Shopify connections are failing with a "HTTP 404 Not Found" errorThis incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connections are syncing successfully. <b>Incident Summary</b> Description: We identified an issue…1h 47mResolved
May 29, 2026Fivetran: Hybrid Deployment Agent jobs failing to start with error "Connection pool shut down"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…7h 19mResolved
May 26, 20263rd Party: Google Display & Video 360 connections are failing with "HTTP 502 Bad Gateway" errorThis incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully. <b>Incident Summary</b> Description: We identified an issue with…6h 28mResolved
May 22, 20263rd Party: Multiple connection syncs are failing with an "Internal: Failed to read token" error.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…11 minResolved
May 22, 20263rd Party: Multiple Salesforce and Salesforce Sandbox connections are failing with HTTP 503 Service UnavailableThis 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…2h 28mResolved
May 22, 20263rd Party: Delay in User facing logs and External logs deliveryThis incident has been resolved. Log processing delay is back to normal. Incident Summary Description: We identified an issue causing a delay in User facing logs and External logs delivery. Timeline: This issue began…2h 7mResolved
May 21, 2026Fivetran: Qualtrics connection syncs are failing with "HTTP 400 Bad Request" for the "TransactionBatches" endpointThis 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…6h 51mResolved
May 20, 20263rd Party: Twitter Ads connections are failing with BadRequestException due to changes on the source side.This incident has been resolved.3h 46mResolved
May 19, 2026Fivetran: Multiple connection syncs are failing with a "Token not found" errorDescription: We identified an issue where connections were intermittently failing with the error message: "UNAUTHENTICATED: Token not found". Timeline: The issue began on 2026-05-19 at 08:48 UTC and was resolved on…25 minResolved
May 18, 2026Fivetran: Mutliple Amazon Ads connection syncs are faling with 'operationTimestamp' NullPointerExceptionThis incident has been resolved. We have observed that success rates are returning to normal levels, and affected connections are syncing successfully. Incident Summary Description: We identified an issue with Amazon…1h 33mResolved
May 16, 2026Fivetran: Facebook Pages connectors failing with MonetizationMetricUnavailableExceptionThis incident has been resolved. We have observed that instance rates have returned to normal levels and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue for…4h 19mResolved
May 13, 20263rd Party: X Ads and X Organic Performance DegradationX has confirmed that the root cause originates within their API environment and they are actively working towards complete resolution.  While the fix must be implemented on their side, Fivetran continues to actively…1056h 37mResolved
May 13, 20263rd Party: Multiple Apple App Store Connections are failing with `Reporter is currently unavailable`This incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue with the…2h 59mResolved
May 12, 20263rd Party: Brevo Connections Experiencing Sync FailuresDescription: We identified an issue with the Brevo connector, which resulted in syncs failing with error: "Invalid date-time filter". Timeline: This issue began on 2026-05-08 16:30:00 UTC and was resolved on 2026-05-12…-5872 minResolved
May 12, 2026Fivetran: Delay in notifications/alerts on the Fivetran dashboardThis incident has been resolved. Incident Summary Description: We identified an issue causing a delay in notifications/alerts on the Fivetran dashboard. Timeline: This issue began on 12th May 04:40 AM UTC and was…22 minResolved
May 11, 20263rd Party: Typeform connections are failing with an error due to changes on the source side in the response for FORM_INSIGHT data.This incident has been resolved, and syncs have recovered.3h 16mResolved
May 10, 2026Fivetran: Marketo Connections Experiencing Sync FailuresThis incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: Affected Marketo connections…2h 28mResolved
May 10, 20263rd Party: Talkdesk connections are failing with "HTTP 404: Report file not found" ErrorThis incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue affecting…7h 21mResolved
May 8, 20263rd Party: Some HubSpot connection syncs are failing with HTTP 500 Internal Server Error and message: "Your HubSpot source is not available at this time. We'll retry the sync later."This incident has been resolved. We have observed that success rates are returning to normal levels and affected connections are syncing successfully. Incident Summary Description: We identified an issue with the…-99 minResolved
May 8, 20263rd Party: Twilio connections are failing with "504 Gateway Timeout ERROR"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 the…1h 19mResolved
May 8, 20263rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server ErrorThis 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 Amazon…6h 36mResolved
May 8, 20263rd Party: Hubspot connection syncs are failing with "HTTP 500 Internal Server Error" and message: "Your HubSpot source is not available at this time. We'll retry the sync later."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 the…1h 9mResolved
May 7, 20263rd Party: Klaviyo connection syncs are failing with Reconnect ErrorThis 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…4h 41mResolved
May 4, 2026Fivetran: Many Connector SDK connections failed syncs with error "Failed to pull image after max retries"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…2h 38mResolved
May 4, 2026Fivetran: Hybrid connections are delayedDescription: We identified connection issues affecting dependency retrieval during the build process for Hybrid Connector images. Specifically, requests to external package sources were failing, resulting in build…4h 6mResolved
May 4, 2026Fivetran: The Connector SDK Connection state not advancingThis incident has been resolved. <b>Incident Summary</b> Description: We identified an issue where the connector SDK connection state is not advancing, resulting in the same data sync for the last few…3h 31mResolved
May 1, 20263rd Party: Hubspot connection syncs are failing with error "Your HubSpot source is not responding at this time. We'll retry the sync later"Instance rates have returned to normal levels, and affected connections are now syncing successfully. Incident Summary Description: We identified an issue impacting HubSpot connections, where syncs started failing…2h 53mResolved
Apr 30, 2026Fivetran: Syncs Are Intermittently Failing with "UNAUTHENTICATED: Token" Errors<b> Incident Summary </b> Description: We identified an issue where services were intermittently failing with the error: "UNAUTHENTICATED: Token", resulting in connector sync failures during specific time…-70 minResolved
Apr 28, 20263rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server ErrorThis incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. <b>Incident Summary</b> Description: We identified an issue with Amazon Selling Partner…4h 17mResolved
Apr 28, 20263rd Party: Qualtrics connector syncs failing with error "Ticket export failed."Instance rates have returned to normal levels, and affected connectors are now syncing successfully. <b>Incident Summary</b> Description: We identified an issue with Qualtrics connections where syncs were failing with…2h 48mResolved
Apr 28, 2026Fivetran: SharePoint and Microsoft Lists connections are failing with error "Authentication failed: The client secret or certificate has expired"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…13h 46mResolved
Apr 28, 20263rd Party: Amazon Selling Partner Connection syncs are failing with 500 Internal Server ErrorThis incident has been resolved. We observed that syncs have recovered and are completing successfully without further failures. <b>Incident Summary</b> Description: We identified an issue with Amazon Selling Partner…2h 17mResolved
Apr 27, 20263rd Party: All Amazon Selling Partner connections are rescheduled due to rate limit changesThis 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…7h 21mResolved
Apr 25, 20263rd Party: Multiple Twitter Ads connections failing due to 500 errorsIncident Summary: Description: Multiple Twitter Ads connectors failed due to the Twitter Ads API returning persistent server errors (HTTP 500) on reporting endpoints. Timeline (UTC): Started at 25.04.2026 21:00 and…14h 35mResolved
Apr 24, 20263rd Party: Sync start delays caused by Azure outage in East-US-2 regionSyncs have returned to normal and Azure looks to have completed the rollout of their fix. Azure will have a post mortem posted to their status page for the root cause of this incident…4h 14mResolved
Apr 23, 20263rd Party: Some Recharge connections are intermittently failing with 502 errorsWe have observed that instance rates have returned to normal levels, and the affected connectors are now syncing successfully. <b>Incident Summary</b> Description: We identified an issue with Recharge connections…-124 minResolved
Apr 23, 20263rd Party: Some ServiceTitan connections are intermittently failing with an HTTP 500 ErrorDescription: We identified an issue affecting ServiceTitan connectors, which resulted in syncs failing with an HTTP 500 error. Timeline: This issue began on 2026-04-23 at 17:55 UTC and was resolved on 2026-04-23 at…-106 minResolved
Apr 23, 2026Fivetran: Some syncs are failing starting at 8AM Pacific time.We have resolved this incident.2h 19mResolved
Apr 21, 20263rd Party: Multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453)This incident has been resolved. We have observed that error rates have returned to normal levels, and the service is operating as expected. Incident Summary Description: We identified an issue affecting multiple…5h 24mResolved
Apr 21, 20263rd Party: Apple App Store Connectors are failing with `Reporter is currently unavailable`We have resolved this incident. Incident Summary Description: We identified an issue affecting Apple App Store connections, which were failing with the error: “Unknown failure. This request can not be processed right…10 minResolved
Apr 16, 2026Fivetran: Hybrid deployment syncs are delayedThis incident has been resolved. <b>Incident Summary</b> Description: We identified an issue where connectors using the Hybrid Deployment agent were unable to schedule new sync jobs. Timeline: This issue began on…0 minResolved
Apr 14, 20263rd Party: Some Twitter Ads connections are failing due to a null primary key exceptionThis 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 Twitter…7h 21mResolved
Apr 11, 20263rd Party: Twitter Ads and Twitter Organic connector sync failures due to Bad Authentication data (code 215) errorThis incident has been resolved. Incident Summary Description: Twitter API started returning a Bad Authentication data error (code 215) while fetching successful async job results. Timeline: Impact start time around…3h 51mResolved
Apr 11, 20263rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to URI is not absolute error with HTTP 500 ResponseIncident Summary. Description: Twitter API started returning Internal Server Error with code 500 when we try to fetch reports. Timeline: Impact start time around April 10th 21:54:44 UTC to April 11th 12:47:37…2h 53mResolved
Apr 10, 2026Fivetran: Transformation jobs are failing with "UnsatisfiedDependencyException" errorThis incident has been resolved. Incident Summary Description: We identified an issue where dbt core and Quickstart transformation jobs are failing with "UnsatisfiedDependencyException" error. Timeline: The issue…1h 11mResolved
Apr 8, 20263rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) errorThis incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connectors are syncing successfully. <b>Incident Summary</b> Description: We identified an issue with…-1268 minResolved
Apr 8, 2026Fivetran: Fivetran : Few Amazon Selling partner connections are failing for the all_listings_reportThis 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…3h 2mResolved
Apr 7, 20263rd Party: Delay in log delivery in customer's external log due to an issue with our external logging servicesThis 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…-354 minResolved
Apr 4, 20263rd Party: Awin connection syncs are failing with 500 internal server error for transaction endpointThis 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…5h 5mResolved
Apr 2, 20263rd Party: Snapchat Ads connections failing with "SSLHandshakeException"This incident has been fully resolved. Error rates have returned to normal levels, and all affected connections are now running successfully. <b>Incident Summary</b> Description: We identified an issue where Snapchat…-29 minResolved
Apr 2, 2026Fivetran: SQL Server TELEPORT and Epic CSA Connector POTENTIAL Failures Due to Unsupported Type in VIEW tablesThis incident has been resolved. Incident Summary Description: We identified an issue affecting the SQL Server (Teleport) and Epic CSA connectors, where syncs were failing with the following…3h 37mResolved

How to Read This Fivetran Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Fivetran acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Fivetran outage in this window ran 44d, against a mean recovery of 1d. If you depend on Fivetran in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.