Fivetran incident
3rd Party: Multiple Twitter Ads connections are failing with an HTTP 500 Internal Server Error
Resolved after 7 hours 11 minutes, affecting X Ads, on April 2, 2026.
A fix has been implemented and the connections are recovering from the failure. We'll continue to monitor the results.
Affected components
Update timeline
- identified Apr 02, 2026, 10:20 AM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 02, 2026, 10:29 AM UTC
We have identified that this issue was caused by the 'campaigns' endpoint, which is returning a '500 Internal Server' error. We are looking into potential workarounds to address these failures and will provide further updates as soon as more information is available.
- monitoring Apr 02, 2026, 02:40 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 02, 2026, 02:51 PM UTC
A fix has been implemented and the connections are recovering from the failure. We'll continue to monitor the results.
- resolved Apr 02, 2026, 05:40 PM UTC
We have resolved this incident.
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