Fivetran incident

Multiple connection syncs are failing with an "Internal: Failed to read token" error.

Minor Resolved View vendor source →

Fivetran experienced a minor incident on May 22, 2026 affecting General Services, lasting 11m. The incident has been resolved; the full update timeline is below.

Started
May 22, 2026, 05:05 AM UTC
Resolved
May 22, 2026, 05:16 AM UTC
Duration
11m
Detected by Pingoru
May 22, 2026, 05:05 AM UTC

Affected components

General Services

Update timeline

  1. identified May 22, 2026, 05:05 AM UTC

    The issue has been identified and we are working to resolve it.

  2. monitoring May 22, 2026, 05:05 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 22, 2026, 05:16 AM UTC

    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.