FIVETRAN

🟠 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)

⏰ May 29, 2026 Fixed (for now) spotted via status_rss

// The official story

Hybrid Deployment Agent jobs failing to start with error "Connection pool shut down"

// Status page says

May 29 , 21:44 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 29 , 21:30 UTC Update - The hot fix should be reflected in the new HD agent images. For existing HD agents, restarting the controller should resolve the issue. Customers are advised to restart their controller with the following commands: cd ~/fivetran<br

🔗 Official status page (for the PR-approved version)

https://status.fivetran.com/incidents/c5jxdzdf7bz2

Fivetran'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 22, 2026

⚪ Fivetran's Salesforce connectors got ghosted by the CRM gods with HTTP 503s. The good news: it's fixed. The bad news: your syncs spent the better part of a day in purgatory. 🍺. (Auto-resolved: no updates in 24h)