Fivetran incident
Fivetran: MySQL connectors using Teleport are failing with the error: “Some tables failed to sync.”
Affected components
Update timeline
- identified Mar 11, 2026, 05:15 AM UTC
The issue has been identified and we are working to resolve it.
- identified Mar 11, 2026, 05:50 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 11, 2026, 05:51 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 11, 2026, 07:43 AM UTC
We have identified the root cause of the issue and are actively working on a hotfix to resolve it.
- monitoring Mar 11, 2026, 09:13 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 11, 2026, 09:41 AM UTC
This incident has now been resolved. We have confirmed that the affected connectors are running successfully and operating as expected. Incident Summary Description: We identified an issue where MySQL connectors using Teleport were failing with the error: “Some tables failed to sync.” Timeline: The issue began on March 11, 2026 at 01:00 UTC and was fully resolved on March 11, 2026 at 09:15 UTC. Cause: The issue was caused by a recent code change made to the connector. Resolution: Engineering identified the root cause and reverted the recent changes. After deploying the revert and a hotfix, the connectors resumed normal operation.
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