Fivetran incident

Fivetran: Multiple connection syncs and transformations are delayed

Resolved after 4 hours 36 minutes, affecting Transformations and General Services, on March 15, 2026.

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.

Started
Mar 15, 2026, 07:35 AM UTC
Resolved
Mar 15, 2026, 12:12 PM UTC
Duration
4h 36m
Detected by Pingoru
Mar 15, 2026, 07:35 AM UTC

Affected components

TransformationsGeneral Services

Update timeline

  1. identified Mar 15, 2026, 07:35 AM UTC

    We have identified an issue where multiple connection syncs and transformations are delayed.

  2. identified Mar 15, 2026, 09:00 AM UTC

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

  3. monitoring Mar 15, 2026, 09:56 AM UTC

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

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

Your product runs on more than Fivetran

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →