Multiple Fivetran Twitter Ads connectors failed for 14.6 hours due to the Twitter Ads API returning persistent HTTP 500 server errors on reporting endpoints. Fivetran deployed a fix that enables connectors to gracefully handle these API errors by skipping affected accounts with dashboard warnings while preserving sync progress for successful accounts. Skipped data will be automatically retried on the next sync cycle.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Incident Summary:
Description:
Multiple Twitter Ads connectors failed due to the Twitter Ads API returning persistent server errors (HTTP 500) on reporting endpoints.
Timeline (UTC):
Started at 25.04.2026 21:00 and Resolved 26.04.2026 11:50
Cause:
The Twitter Ads API experienced an outage, returning repeated HTTP 500 Internal Server errors on the stats reporting endpoint (POST URI https://ads-api.twitter.com/12/stats/jobs/accounts/).
Resolution:
Deployed a fix/workaround that enables the connector to gracefully handle HTTP 500 errors from the Twitter Ads API. Affected accounts are now skipped with a customer-facing warning on the connector dashboard, sync progress is preserved for successful accounts, and skipped data is automatically retried on the next sync.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.
The issue has been identified and we are working to resolve it.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with