Fivetran incident

3rd Party: Some Recharge connections are intermittently failing with 502 errors

Notice Resolved View vendor source →
Started
Apr 23, 2026, 08:04 PM UTC
Resolved
Apr 23, 2026, 06:00 PM UTC
Duration
—
Detected by Pingoru
Apr 23, 2026, 08:04 PM UTC

Update timeline

  1. resolved Apr 23, 2026, 08:04 PM UTC

    We have observed that instance rates have returned to normal levels, and the affected connectors are now syncing successfully. Incident Summary Description: We identified an issue with Recharge connections, where syncs were failing with a 502 error. Timeline: The issue began on 2026-04-23 at 15:45 UTC and was resolved at 17:38 UTC. Cause: The failures were caused by the intermittent unavailability of the Recharge API, leading to sync disruptions. More details are available on the recharge's status page: https://status.getrecharge.com/incidents/cbz3mcgf2lx5 Resolution: The issue was resolved automatically once the Recharge API resumed normal operation

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