Fivetran incident
3rd Party: Sync start delays caused by Azure outage in East-US-2 region
Resolved after 4 hours 14 minutes, affecting General Services, on April 24, 2026.
Syncs have returned to normal and Azure looks to have completed the rollout of their fix. Azure will have a post mortem posted to their status page for the root cause of this incident: https://azure.status.microsoft/en-us/status
Affected components
Update timeline
- identified Apr 24, 2026, 06:35 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 24, 2026, 06:58 PM UTC
The issue was caused by an outage on Azure. You can find more details at the following link: https://azure.status.microsoft/en-us/status
- identified Apr 24, 2026, 08:47 PM UTC
Azure has identified the issue and they expect recovery within the next hour. Fivetran engineering will continue to monitor as Azure works through this incident.
- identified Apr 24, 2026, 09:49 PM UTC
Azure is continuing to rollout a fix in the East US region. We have observed our backlog of syncs are caught up, but pod scaling is still affected. Once Azure confirms they have competed their fix, we will test pod scaling to ensure it works as expected.
- resolved Apr 24, 2026, 10:50 PM UTC
Syncs have returned to normal and Azure looks to have completed the rollout of their fix. Azure will have a post mortem posted to their status page for the root cause of this incident: https://azure.status.microsoft/en-us/status
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.
Amazon Web Services