← Back to the carnage
FIVETRAN
🟠 Azure's regional infrastructure in East-US-2 decided to ghost everyone's data pipelines. Fivetran customers got to experience the classic 'waiting for someone else's infrastructure to unfail' experience. Azure eventually found the off-switch and syncs limped back online. (Auto-resolved: no updates in 24h)
// The official story
3rd Party: Sync start delays caused by Azure outage in East-US-2 region
// Status page says
Apr 24 , 22:50 UTC Resolved - 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 Apr 24 , 21:49 UTC Update - Azure is continuing to rollout a fix in the East US region. We have observed our backlo
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/cn6sd4rcj1lwFivetran's Greatest Hits
🟢 FIVETRAN
Jun 14, 2026
🟠 Multiple Customer.io connections are throwing 5xx errors like confetti. Fivetran implemented a skip mechanism, but the issue just migrated from job creation to report downloads—classic adversary-with-a-moving-target situation. Engineers are monitoring like hawks, hoping the problem doesn't develop new attack patterns. (Auto-resolved: no updates in 24h)
🟢 FIVETRAN
Jun 03, 2026
🔴 Fivetran's Shopify integration joined the broken API club after Shopify's own endpoints decided 404s were this week's personality. Your data pipeline is now a data paperweight until someone fixes upstream. (Auto-resolved: no updates in 24h)
🟢 FIVETRAN
May 29, 2026
🟠 Fivetran's HD Agent jobs decided connection pools were too mainstream and ghosted them entirely. The fix? Turn it off and on again—because apparently even data infrastructure needs a nap. Engineers are now nervously watching to confirm the agents remember how to work. (Auto-resolved: no updates in 24h)
🟢 FIVETRAN
May 29, 2026
🟠 Fivetran's HD Agent jobs decided connection pools were overrated and shut themselves down. Engineers deployed a hot fix that works if you manually restart your controller like it's 1997. Monitoring mode: engaged (translation: 'fingers crossed'). (Auto-resolved: no updates in 24h)