Fivetran incident
3rd Party: Twitter Ads and Twitter Organic connector sync failures due to Bad Authentication data (code 215) error
Resolved after 3 hours 51 minutes, affecting X Ads, on April 11, 2026.
This incident has been resolved. Incident Summary Description: Twitter API started returning a Bad Authentication data error (code 215) while fetching successful async job results. Timeline: Impact start time around April 11th, 9:30 PM UTC to April 11th 01:57 UTC Cause: 3rd party error on Twitter side Resolution: We have implemented a workaround that skips the problematic endpoints for problematic accounts when this error occurs, and connectors are now back to normal.
Affected components
Update timeline
- identified Apr 11, 2026, 10:45 PM UTC
The issue has been identified and we are working to resolve it.
- identified Apr 11, 2026, 11:18 PM UTC
Connectors are failing with a “Bad Authentication data” error (code 215) while fetching successful async job results.
- monitoring Apr 12, 2026, 12:07 AM UTC
A fix has been implemented, and we are monitoring the results.
- resolved Apr 12, 2026, 02:36 AM UTC
This incident has been resolved. Incident Summary Description: Twitter API started returning a Bad Authentication data error (code 215) while fetching successful async job results. Timeline: Impact start time around April 11th, 9:30 PM UTC to April 11th 01:57 UTC Cause: 3rd party error on Twitter side Resolution: We have implemented a workaround that skips the problematic endpoints for problematic accounts when this error occurs, and connectors are now 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