Outage in Fivetran
3rd Party: Multiple Twitter and Twitter Ads connections are failing with "HTTP 503 Service Unavailable"
Resolved MinorIncident Report
Summary AI Generated
Fivetran's Twitter and Twitter Ads connections experienced failures with "HTTP 503 Service Unavailable" errors due to a third-party API issue on X (Twitter)'s side. The incident affected Twitter Ads components and lasted 10.2 hours from March 26, 2026 01:00 UTC to 14:30 UTC. The issue was resolved when X fixed their API, with connection recovery observed gradually and error rates returning to normal levels.
The issue has been identified and we are working to resolve it.
Components affected
Fivetran Twitter AdsNeed to monitor Fivetran outages?
- Monitor all your external dependencies in one place
- Get instant alerts when outages are detected
- Be the first to know if service is down
- Show real-time status on private or public status page
- Keep your team informed
Latest Updates ( sorted recent to last )
RESOLVED
2 days ago - at 03/26/2026 01:40PM
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.
MONITORING
2 days ago - at 03/26/2026 11:41AM
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
MONITORING
2 days ago - at 03/26/2026 10:40AM
A fix has been implemented and we are monitoring the results.
IDENTIFIED
2 days ago - at 03/26/2026 08:35AM
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.
IDENTIFIED
2 days ago - at 03/26/2026 05:56AM
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.
IDENTIFIED
2 days ago - at 03/26/2026 04:09AM
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.
IDENTIFIED
2 days ago - at 03/26/2026 03:30AM
The issue has been identified and we are working to resolve it.
Latest Fivetran outages
Fivetran: Fivetran REST API Failing with 404 Errors - 2 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with
