← Back to the carnage
FIVETRAN
⚪ 🍎 Apple's App Store connector went radio silent, rejecting everything with a cryptic 'Reporter is currently unavailable' error. Fivetran engineers played tech support therapist for 2.5 hours until Apple remembered how to answer the phone. (Auto-resolved: no updates in 24h)
// The official story
3rd Party: Apple App Store Connectors are failing with `Reporter is currently unavailable`
// Status page says
Apr 21 , 04:41 UTC Resolved - We have resolved this incident. Incident Summary Description: We identified an issue affecting Apple App Store connections, which were failing with the error: “Unknown failure. This request can not be processed right now Reporter is currently unavailable.” Timeline: The issue began on April 20th at 22:45 UTC and was resolved on April 21st at 01:20 UTC.
🔗 Official status page (for the PR-approved version)
https://status.fivetran.com/incidents/mpvv07ysyynxFivetran'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)