← Back to the carnage
FIVETRAN
🟠 Fivetran's Workday connectors got ghosted when the source decided to take an unscheduled vacation. Engineers are now in damage control mode, hoping Cupid's arrow finds the fix before your data warehouse files for divorce. (Auto-resolved: no updates in 24h)
// The official story
3rd Party: Workday Connections Failed Due to Source Downtime
// Status page says
Feb 14 , 04:40 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 14 , 04:40 UTC Identified - The issue has been identified and we are working to resolve it.
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/jfb8tbrqmbssFivetran'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)