Fivetran incident

3rd Party: Multiple Twitter Ads connections are failing with an HTTP 500 Internal Server Error

Minor Resolved View vendor source →
Started
Apr 02, 2026, 10:29 AM UTC
Resolved
Apr 02, 2026, 05:40 PM UTC
Duration
7h 11m
Detected by Pingoru
Apr 02, 2026, 10:29 AM UTC

Affected components

Twitter Ads

Update timeline

  1. identified Apr 02, 2026, 10:20 AM UTC

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

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

  3. monitoring Apr 02, 2026, 02:40 PM UTC

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

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

  5. resolved Apr 02, 2026, 05:40 PM UTC

    We have resolved this incident.

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