Fivetran incident

3rd Party: Failures Triggering Connection Syncs via API and Dashboard

Notice Resolved View vendor source →

Fivetran experienced a notice incident on June 8, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2026, 10:00 PM UTC
Resolved
Jun 08, 2026, 10:00 PM UTC
Duration
—
Detected by Pingoru
Jun 08, 2026, 10:00 PM UTC

Update timeline

  1. resolved Jun 09, 2026, 12:34 PM UTC

    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.