3rd Party: Multiple Twitter Ads and Twitter Organic Connections Failing with error "HTTP 503 Service Unavailable"

Update timeline

1. identified Mar 30, 2026, 05:55 PM UTC

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

2. identified Mar 30, 2026, 06:09 PM UTC

   The issue appears to be related to missing rate limit headers in the response. As a result, requests are repeatedly hitting HTTP 429 (rate limit) and, in some cases, resulting in HTTP 503 errors. We have reached out to X support, and X has also acknowledged degraded performance on their status page: https://docs.x.com/status

3. identified Mar 31, 2026, 03:56 AM UTC

   We are still seeing the issue at the source end and are continuing to monitor their status page. We have reached out to X support, and X has acknowledged degraded performance on their status page: https://docs.x.com/status.

4. identified Mar 31, 2026, 11:56 AM UTC

   We are continuing to monitor the status page, as there are no latest updates from X. In the meantime, we are exploring potential workarounds to help mitigate the issue until it is fully resolved on the source side.

5. monitoring Mar 31, 2026, 03:54 PM UTC

   The issue appears to have been resolved from the source side. Rate limit errors have subsided, and affected connectors have returned to normal sync operations

6. resolved Mar 31, 2026, 05:25 PM UTC

   This incident has been resolved. We have observed that error rates have returned to normal levels, and the Twitter Organic and Twitter Ads services are operating as expected. Incident Summary Description: We identified an issue affecting multiple Twitter Organic and Twitter Ads connections, which were failing with the error: “HTTP 503 Service Unavailable.” Timeline: The issue began on March 30th at 00:00 UTC and was resolved on March 31st at 16:30 UTC. Cause: The X API stopped returning rate limit information in the response headers. This caused Twitter Organic and Twitter Ads connections to encounter 429 errors, leading to sync failures. Resolution: X has resolved their API issue. Additionally, we deployed a hotfix to ensure that if the source hits account-level rate limits and does not return response headers, it will no longer cause sync failures. Instead, the connections will be automatically rescheduled.