🔴 Salesforce decided to stop accepting Fivetran's calls at 1:20 AM UTC. Multiple connections now getting the HTTP 503 treatment—which is corporate for 'we're not home right now.' Engineers are investigating whether this is a feature or a bug. (Auto-resolved: no updates in 24h)

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