Fivetran Outage History

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected Ramp connections are syncing successfully. Incident Summary Description: We identified an issue affecting Ramp connections that caused sync failures due to repeated HTTP 529 responses from the source API. Timeline: The issue began on 2026-07-10 at 16:50 UTC and was resolved on 2026-07-10 at 19:30 UTC. Cause: The source API was repeatedly returning HTTP 529 responses across multiple endpoints, resulting in sync failures. Resolution: No action was required from our side. The issue was resolved by the source, and affected connections recovered automatically once the source API resumed returning successful responses.

This incident has been resolved. We have observed that error rates have returned to normal levels, and all affected connectors are syncing successfully. Incident Summary Description: We identified an issue affecting QuickBooks connections that caused syncs to fail for the CreditCardPaymentTxn entity. Timeline: The issue began on 2026-07-07 at 2:00 PM UTC and was resolved on 2026-07-07 at 7:10 PM UTC. Cause: The QuickBooks query entity was changed from CreditCardPaymentTxn to CreditCardPayment, causing API requests made by the connector to fail with a 400 ValidationFault. Resolution: We made the required changes for the connector to use the new CreditCardPayment query entity. After deploying this change, the affected connectors recovered successfully, and syncs resumed normal operation.

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 reached out to the Impact source team to investigate the 500 Internal Server Errors. The issue has now been resolved on the Impact side, and no action was taken from Fivetran.

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.

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.

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 Saleforce Connection which resulted in syncs failing with a HTTP 503 Service Unavailable error. Timeline: This issue began on 21 May 2026 at 20:00 UTC and was resolved on 22 May 2026 at 00:30 UTC. Cause: The failures were caused by a source-side outage in the Saleforce API, resulting in 500 Internal Server Error responses. Resolution: No action was taken from our end. The issue was resolved on the source side, and syncs recovered automatically.

This 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 on 22nd May 00:00 UTC and was resolved on 22nd May 2:40 UTC. Cause: Misconfiguration in one of our services has caused the issue. Resolution: We have disabled the problematic part to fix the issue.

We have resolved this incident.

This incident has been resolved.

Description: 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 2026-05-19 at 09:10 UTC. During this period, customers may have experienced intermittent sync failures, with services recovering shortly afterwards. Root Cause: The issue was caused by failures within the scheduling layer due to an internal network disruption. This resulted in cascading failures across dependent connection services. Resolution: The affected connections recovered once network connectivity was restored. All services are currently operating normally.

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 Amazon Ads connections that caused syncs to fail with a 'operationTimestamp' NullPointerException. Timeline: This issue began on 18-05-2026 04:49 AM UTC and was resolved on 18-05-2026 08:08 AM UTC. Cause: A recent change related to Operations Consolidation introduced a regression, causing a null pointer exception and resulting in sync failures for affected Amazon Ads connectors. Resolution: We reverted the change that was causing the issue, after which syncs started succeeding.

This incident has been resolved. We have observed that instance rates have returned to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for Facebook Pages which resulted in syncs failing with an An unknown error has occurred error while fetching monetization metrics. Timeline: This issue began on 2026-05-15 at 16:30 UTC and was resolved on 2026-05-16 at 17:55 UTC. Cause: An added monetization metrics path in Facebook Pages was unstable and occasionally failed when Facebook returned a transient error, which caused syncs to fail. Resolution: We disabled monetization metrics processing for Facebook Pages connector, which stopped the failing requests and allowed affected connectors to recover.

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 Apple App Store connection, which resulted in syncs failing with `Reporter is currently unavailable` Timeline: This issue began on 2026-05-12T22:32:00Z UTC and was resolved on 2026-05-13T02:45:00Z UTC. Cause: The issue was caused by the third-party, /v1/financeReports endpoint failing with "HTTP 503 SERVICE_UNAVAILABLE_ERROR: Reporter is currently unavailable. Resolution: The issue was automatically resolved from the third-party side without any intervention from the Fivetran end.

Description: 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 07:00:00 UTC. Cause: A recent update from Brevo resulted in the date format that the connector used being incompatible with the source API requirements. Resolution: The datetime formatter has been updated to ensure timestamps are always sent in explicit UTC format (Z) as expected by the source API. This resolved the connector failures and also handles any potential format variation going forward.

This 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 resolved on 12th May 06:19 AM UTC. Cause: A recent code change on the Fivetran side has caused this issue. Resolution: The code change has been reverted to fix the issue.

This incident has been resolved, and syncs have recovered.