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

Incident Report for Fivetran

Resolved

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

Posted Apr 23, 2026 - 18:00 UTC