Fivetran incident
3rd Party: Multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453)
Affected components
Update timeline
- identified Apr 21, 2026, 10:00 PM UTC
The issue has been identified and we are working to resolve it.
- monitoring Apr 22, 2026, 12:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 22, 2026, 03:25 AM UTC
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 affecting multiple Twitter Ads Connections Sync Failures Due to Access Level/Permission Error (Code 453) Timeline: The issue began on 2026-04-21 20:43 UTC and was resolved on 2026-04-22 02:23 UTC. Cause: X API started to fail report GZIP file authenticated download requests. Resolution: Authentication has been removed from GZIP file download requests.
Looking to track Fivetran downtime and outages?
Pingoru polls Fivetran's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Fivetran reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Fivetran alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required