FIVETRAN

⚪ Fivetran's Criteo connector spent an hour returning 503s and 504s while Criteo had what we in the industry call 'a complete meltdown.' The good news? Not Fivetran's problem this time—Criteo's infrastructure decided to take an unscheduled nap. (Auto-resolved: no updates in 24h)

⏰ Mar 30, 2026 Fixed (for now) spotted via status_rss

// The official story

3rd Party: Criteo Connection Sync Failures due to the 503 and 504 errors.

// Status page says

Mar 30 , 10:15 UTC Resolved - Description: We identified an issue affecting the Criteo connector, which resulted in syncs failing with 503 Service Unavailable and 504 Gateway Time-out errors. Timeline: This issue began on March 30, 2026 at 08:17 UTC and was resolved on March 30, 2026 at 09:17 UTC. Cause: The failures were caused by an outage on the Criteo source side, as confirmed on their official

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

https://status.fivetran.com/incidents/998zf60r4qwg

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