Fivetran incident
3rd Party: Some Recharge connections are intermittently failing with 502 errors
Resolved on April 23, 2026.
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
Update timeline
- 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
Your product runs on more than Fivetran
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services