← Back to the carnage
FIVETRAN

🟠 Fivetran's Facebook Pages connectors are throwing MonetizationMetricUnavailableException like they're allergic to money. Turns out even data pipelines can't monetize what doesn't exist. Engineers are investigating whether this is a Facebook API problem or Fivetran just discovered the metric was always imaginary. (Auto-resolved: no updates in 24h)

⏰ May 16, 2026 Fixed (for now) spotted via status_rss

// The official story

Facebook Pages connectors failing with MonetizationMetricUnavailableException

// Status page says

May 16 , 14:25 UTC Identified - The issue has been identified and we are working to resolve it.

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

https://status.fivetran.com/incidents/d2qqfx3yc431

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)