Fivetran incident

3rd Party: Twitter Ads and Twitter Organic connector sync failures due to Bad Authentication data (code 215) error

Minor Resolved View vendor source →
Started
Apr 11, 2026, 10:45 PM UTC
Resolved
Apr 12, 2026, 02:36 AM UTC
Duration
3h 51m
Detected by Pingoru
Apr 11, 2026, 10:45 PM UTC

Affected components

Twitter Ads

Update timeline

  1. identified Apr 11, 2026, 10:45 PM UTC

    The issue has been identified and we are working to resolve it.

  2. 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.

  3. monitoring Apr 12, 2026, 12:07 AM UTC

    A fix has been implemented, and we are monitoring the results.

  4. 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.

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
Start monitoring Fivetran for free

5 free monitors · No credit card required