3rd Party: Multiple Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable"
Incident
Report for Fivetran
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.
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.
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
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
Monitoring
A fix has been implemented and we are monitoring the results.
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.
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.
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.
We are continuing to closely monitor the situation and will keep you informed as soon as we receive any new information.
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.
https://docs.x.com/status
We are closely monitoring the situation and will provide further updates as soon as more information becomes available.
Identified
The issue has been identified and we are working to resolve it.
This incident affected: Marketing connectors (X Ads).