← Back to the carnage
FIVETRAN
⚪ 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)
// The official story
3rd Party: Multiple Salesforce and Salesforce Sandbox connections are failing with HTTP 503 Service Unavailable
// Status page says
May 22 , 05:04 UTC Resolved - This incident has been resolved. We have observed that instance rates are returning to normal levels and affected connectors are syncing successfully. Incident Summary Description: We identified an issue for Saleforce Connection which resulted in syncs failing with a HTTP 503 Service Unavailable error. Timeline: This issue began on 21 May 2026 at 20:00 UTC and wa
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/8j2zdpdqv78pFivetran'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)