Fivetran incident
3rd Party: Snowflake Downtime Causing Sync Failures Across Multiple Connections Using Snowflake as Destination
Fivetran experienced a minor incident on March 21, 2026 affecting Destinations and General Services, lasting 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Mar 21, 2026, 07:05 AM UTC
The issue has been identified and we are working to resolve it.
- identified Mar 21, 2026, 07:07 AM UTC
Sync failures were caused by an ongoing Snowflake issue impacting Snowflake destinations. Snowflake has reported recovery for US regions, and we are monitoring to ensure all syncs return to normal. More details: https://status.snowflake.com/
- monitoring Mar 21, 2026, 07:30 AM UTC
Snowflake has reported recovery for US regions, and we are monitoring to ensure all syncs return to normal. More details: https://status.snowflake.com/
- monitoring Mar 21, 2026, 09:38 AM UTC
We are continuing to monitor to ensure all syncs return to normal. More details: https://status.snowflake.com/
- resolved Mar 21, 2026, 10:30 AM 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 where multiple connection syncs under the Snowflake destination are failing due to a Snowflake Downtime. Timeline: This issue began on 21-03-2026 at 05:26:30 UTC and was resolved on 21-03-2026 at 06:17:30 UTC. Cause: External Snowflake incident affecting the impacted AWS region(s), leading to elevated Snowflake exceptions and downstream sync failures. Resolution: The issue was resolved on the Snowflake side, and connections are now syncing successfully