Fivetran incident
3rd Party: Twitter Ads and Twitter Organic connections are experiencing sync failures due to URI is not absolute error with HTTP 500 Response
Resolved after 2 hours 53 minutes, affecting X Ads, on April 11, 2026.
Incident Summary. Description: Twitter API started returning Internal Server Error with code 500 when we try to fetch reports. Timeline: Impact start time around April 10th 21:54:44 UTC to April 11th 12:47:37 UTC Cause: 3rd party error on twitter side Resolution: We have implemented a workaround for this by skipping reports for problematic accounts and connectors are back to normal.
Affected components
Update timeline
- identified Apr 11, 2026, 11:55 AM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 11, 2026, 01:08 PM UTC
The failure, "URI is not absolute" is a cause of failing Twitter APIs while trying to fetch reports with code 500 and message "internal server error"
- monitoring Apr 11, 2026, 01:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 11, 2026, 02:48 PM UTC
Incident Summary. Description: Twitter API started returning Internal Server Error with code 500 when we try to fetch reports. Timeline: Impact start time around April 10th 21:54:44 UTC to April 11th 12:47:37 UTC Cause: 3rd party error on twitter side Resolution: We have implemented a workaround for this by skipping reports for problematic accounts and connectors are back to normal.
Your product runs on more than Fivetran
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services