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 →

Fivetran experienced a notice incident on April 8, 2026, lasting —. The incident has been resolved; the full update timeline is below.

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.