Resolved -
This incident has been resolved. We have observed that error rates have returned to normal levels, and the service is operating as expected.
Incident Summary
Description:
We identified an issue with the multiple Twitter and Twitter Ads connections, which are failing with the error "HTTP 503 Service Unavailable".
Timeline:
The issue began on 26/03/2026 at 01:00 UTC and was resolved on 26/03/2026 at 14:30 UTC.
Cause:
A third-party issue caused Twitter and Twitter_Ads connections to fail.
Resolution:
X (Twitter) has fixed their API.
Mar 26, 13:40 UTC
Update -
Many Twitter and Twitter Ads connections have recovered, and the rate of severe errors has dropped significantly over the past 2 hours.
We are still seeing intermittent 500 and 503 errors for a small subset of connections.
X (Twitter) has not yet marked the incident as resolved on their status page, and we will continue to monitor for full recovery.
https://docs.x.com/status
Mar 26, 11:41 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 26, 10:40 UTC
Update -
We have reached out to the third-party to obtain the latest status on this issue and are currently awaiting their response.
Additionally, we have started observing "HTTP 500 – Internal Server Error" for a few connections.
At this time, there are no further updates available on their status page. We are continuing to closely monitor the situation and will share updates as soon as we receive more information.
Mar 26, 08:35 UTC
Update -
The third-party is still working on this incident, and there have been no further updates on their status page at this time.
We are continuing to closely monitor the situation and will keep you informed as soon as we receive any new information.
Mar 26, 05:56 UTC
Update -
The issue has been identified as being caused by a problem on the third-party side. They have also acknowledged and posted an update on their page (link below).
https://docs.x.com/status
We are closely monitoring the situation and will provide further updates as soon as more information becomes available.
Mar 26, 04:09 UTC
Identified -
The issue has been identified and we are working to resolve it.
Mar 26, 03:30 UTC