← Back to the carnage
FIVETRAN
🟠 Fivetran's Twitter Ads pipeline joined the 'data goes in, null comes out' club when Twitter's API went full zen. A hotfix has been deployed, connections are limping back, and engineers are nervously watching like parents waiting for test scores. (Auto-resolved: no updates in 24h)
// The official story
Some Twitter Ads connections are failing due to a null primary key exception
// Status page says
Apr 14 , 22:48 UTC Monitoring - Twitter has identified an outage and services have now returned to normal: https://devcommunity.x.com/t/x-api-service-outage/262778 A hotfix has also been deployed to prevent further failures due to null primary keys. We have observed connections begin to recover and will continue monitoring. Apr 14 , 19:21 UTC Update - We h
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/stb7x9yvwq1rFivetran'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)