← Back to the carnage
FIVETRAN
🟠 Fivetran decided properties are optional—connections and transformations started ghosting users hard. Engineers deployed a hot fix to resurrect the stable versions and error rates finally remembered how to go to zero. (Auto-resolved: no updates in 24h)
// The official story
Fivetran: Multiple connection and tranformation failures observed with error message: No such property isActive
// Status page says
Jan 27 , 17:39 UTC Update - The error rate has returned down to 0 and we are continuing to observe new transformations and syncs. Jan 27 , 15:50 UTC Monitoring - We have released an update to ensure only the stable versions of these services are active. We are currently monitoring sync success rates and transformation runs to ensure all affected services resume normal func
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/7z90w9lmcgbvFivetran'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)