Multiple Twitter Ads and Twitter Organic Connections Failing with error "HTTP 503 Service Unavailable"
Incident Lifecycle
Incident Timeline
Monitoring
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
Mar 31, 2026 at 3:54 PM UTC
Identified
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.
In the meantime, we are exploring potential workarounds to help mitigate the issue until it is fully resolved on the source side.
Mar 31, 2026 at 11:56 AM UTC
Identified
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.
Mar 31, 2026 at 3:56 AM UTC
Identified
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
Mar 30, 2026 at 6:09 PM UTC
Identified
The issue has been identified and we are working to resolve it.
Mar 30, 2026 at 5:55 PM UTC
Was your business affected by this Fivetran outage?
Set up instant alerts for Fivetran — be the first to know about outages via email, Slack, Teams, or Discord.