Fivetran incident

3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to an HTTP 503 (Service Unavailable) error

Notice Resolved View vendor source →
Started
Apr 08, 2026, 08:38 PM UTC
Resolved
Apr 07, 2026, 11:30 PM UTC
Duration
—
Detected by Pingoru
Apr 08, 2026, 08:38 PM UTC

Update timeline

  1. resolved Apr 08, 2026, 08:38 PM UTC

    This incident has been resolved. We have observed that instance rates have returned to normal levels, and affected connectors are syncing successfully. Incident Summary Description: We identified an issue with Twitter Ads and Twitter Organic connections, which resulted in sync failures with an "HTTP 503 (Service Unavailable)" error. Timeline: This issue began on 2026-04-07 at 15:00 UTC and was resolved at 23:00 UTC. Cause: The Twitter Ads API '/stats/jobs/accounts/' endpoint started returning HTTP 503 (Service Unavailable) errors. Resolution: A hotfix was deployed to handle 503 errors, as well as to retry failed endpoints.

Looking to track Fivetran downtime and outages?

Pingoru polls Fivetran's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Fivetran reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Fivetran alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Fivetran for free

5 free monitors · No credit card required