Fivetran incident
Fivetran: Multiple connection syncs and transformations are delayed
Affected components
Update timeline
- identified Mar 15, 2026, 07:35 AM UTC
We have identified an issue where multiple connection syncs and transformations are delayed.
- identified Mar 15, 2026, 09:00 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 15, 2026, 09:56 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 15, 2026, 12:12 PM UTC
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 that caused delays in connection syncs and transformations. During this time, new syncs in AWS and Azure were delayed, while ongoing syncs continued to run normally. In the GCP regions, ongoing syncs failed, and new syncs were delayed. Timeline: This issue began on March 15, 2026, at 6:20 UTC and was resolved on March 15, 2026, at 11 UTC. Cause: A recent infrastructure change caused the issue. Resolution: A fix was implemented to address the infrastructure issue, after which instance rates returned to normal, and affected connectors resumed syncing successfully.
Looking to track Fivetran downtime and outages?
Pingoru polls Fivetran's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Fivetran reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Fivetran alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required