Fivetran incident

Fivetran: MySQL connectors using Teleport are failing with the error: “Some tables failed to sync.”

Minor Resolved View vendor source →

Fivetran experienced a minor incident on March 11, 2026 affecting Amazon Aurora MySQL and Azure Database for MySQL and 1 more component, lasting 4h 25m. The incident has been resolved; the full update timeline is below.

Started
Mar 11, 2026, 05:15 AM UTC
Resolved
Mar 11, 2026, 09:41 AM UTC
Duration
4h 25m
Detected by Pingoru
Mar 11, 2026, 05:15 AM UTC

Affected components

Amazon Aurora MySQLAzure Database for MySQLGoogle Cloud SQL for MySQLMagento MySQLMagento MySQL RDSMySQLMySQL RDS

Update timeline

  1. identified Mar 11, 2026, 05:15 AM UTC

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

  2. identified Mar 11, 2026, 05:50 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 11, 2026, 05:51 AM UTC

    We are continuing to work on a fix for this issue.

  4. 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.

  5. monitoring Mar 11, 2026, 09:13 AM UTC

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

  6. 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.