← Back to the carnage
FIVETRAN

🟠 HubSpot's API decided to play hide-and-seek with its own resources, leaving Fivetran connections returning 404s like rejected suitors. The fix is supposedly in, but your syncs are still catching their breath. (Auto-resolved: no updates in 24h)

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

// The official story

3rd Party: Some HubSpot connections intermittently failing with "The requested resource does not exist" error

// Status page says

Mar 5 , 12:31 UTC Update - The issue has been identified as a HubSpot outage that caused temporary unavailability of certain API services. As a result, affected connections experienced intermittent sync failures. HubSpot has implemented a fix, and services are currently recovering. For additional details, please refer to the HubSpot Status Page: https://status.hubspot.com/incidents/9szm40l2fq2s

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

https://status.fivetran.com/incidents/7wckt0t4qkt0

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)