Fivetran Status Page

May 26, 2026 · resolved May 26

This 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 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.

May 22, 2026 · resolved May 22

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.

May 22, 2026 · resolved May 22

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 Salesforce and Salesforce Sandbox Connections 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 Salesforce 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. For any connections still showing a delayed status, we recommend pausing and resuming the connection.

May 22, 2026 · resolved May 22

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.

May 21, 2026 · resolved May 21

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 affecting the Qualtrics connector, which caused syncs to fail with an HTTP 400 Bad Request error for the transactionBatches endpoint. Timeline: This issue began on 2026-05-20 at 08:10 PM UTC and was resolved on 2026-05-21 at 12:30 PM UTC. Cause: We have observed that the API calls were failing due to empty skipToken query parameter that we were passing to the API call. We have reached out to the third-party team since this was a new change Resolution: A fix has been implemented from our end to omit the skipToken parameter whenever its value is empty or null.