← Back to the carnage
FIVETRAN
🔴 FIVETRAN - Fivetran: Intermittent REST API requests timeouts. (Auto-resolved: no updates in 24h)
// The official story
Fivetran: Intermittent REST API requests timeouts.
// Status page says
Mar 26 , 10:00 UTC Resolved - Incident Summary Description: We identified an issue where some Fivetran REST API requests were timing out. Timeline: The issue began on 26/03/2026 at 10:17 UTC and was resolved on 26/03/2026 at 12:05 UTC. Cause: The issue was caused by resource constraints in our infrastructure, causing timeouts when resources were unavailable. Resolution: We have
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/cf71yybxwtdhFivetran'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)