3rd Party: Multiple Twitter Ads connections failing due to 500 errors

Update timeline

1. identified Apr 25, 2026, 10:55 PM UTC

   The issue has been identified and we are working to resolve it.

2. identified Apr 26, 2026, 12:09 AM UTC

   We are receiving 500 Internal Server Errors from the Twitter API when querying the accounts endpoint.

3. identified Apr 26, 2026, 05:48 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Apr 26, 2026, 12:26 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Apr 26, 2026, 01:30 PM UTC

   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.