← Back to the carnage
FIVETRAN
⚪ Twitter's Ads API decided to return nothing but 500 errors for 14+ hours, turning Fivetran connectors into elaborate paperweights. Third-party auth issues are fun until they're not. Resolved after Twitter remembered what 'working' means. (Auto-resolved: no updates in 24h)
// The official story
3rd Party: Multiple Twitter Ads connections failing due to 500 errors
// Status page says
Apr 26 , 13:30 UTC Resolved - Incident Summary: Description: Multiple Twitter Ads connectors failed due to the Twitter Ads API returning persistent server errors (HTTP 500) on reporting endpoints. Timeline (UTC): Started at 25.04.2026 21:00 and Resolved 26.04.2026 11:50 Cause: The Twitter Ads API experienced an outage, returning repeated HTTP 500 Internal Server errors o
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/wyhpznkgtgxtFivetran'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)