Multiple Fivetran connection syncs failed with "Internal: Failed to read token" errors due to transient network issues affecting Google Cloud Platform's Firestore service. The incident impacted General Services and lasted 14 minutes from 02:47 to 05:16 UTC on May 22, 2026. The issue was resolved when the Firestore network problems stabilized, allowing all affected syncs to recover and return to normal operation.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
A fix has been implemented and we are monitoring the results.
The issue has been identified and we are working to resolve it.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with