Recharge Outage History
13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Recharge Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 28, 2026 | Degraded Service PerformanceThis issue is now resolved. | 1h 56m | Resolved |
| Sep 25, 2026 | Systems degradedA fix has been implemented, and we are currently working on data ingest and recharge checkout assessment | 2h 31m | Resolved |
| Sep 1, 2026 | Potential SMS DelaysThe third party provider has resolved their outage. | 39 min | Resolved |
| Aug 7, 2026 | Upcoming Charge Notification DelayThis has been resolved. | 11h 12m | Resolved |
| Jul 20, 2026 | Merchant Admin Access DegradedWe are observing full recovery and will continue monitoring. | 1h 21m | Resolved |
| Jun 29, 2026 | Delayed analytics dataThis has been resolved and data for 6/28/26 is displaying as expected. | 4h 25m | Resolved |
| Apr 29, 2026 | Third party provider webhook issueThis issue has been resolved. | 6h 31m | Resolved |
| Apr 23, 2026 | Merchant Admin Access DegradedThis incident has been resolved. | 46 min | Resolved |
| Apr 7, 2026 | Analytics daily refresh failed impacting data exports.The issue with the Merchant Analytics data refresh is fixed. All data is now refreshed. | 4h 2m | Resolved |
| Feb 12, 2026 | Renew Rate Dashboard ErrorThis error has been resolved. | 18 min | Resolved |
| Dec 17, 2025 | Degraded Admin AccessibilityThis incident has been resolved. | 1h 2m | Resolved |
| Dec 16, 2025 | API degradation across several servicesThis has been resolved. | 1h 32m | Resolved |
| Nov 9, 2025 | Issue with charge processingThe root cause of this incident has been resolved. Those impacted will receive further communication. | 78h 29m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Recharge incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Recharge Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Recharge acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Recharge outage in this window ran 3d 6h, against a mean recovery of 8h 50m. If you depend on Recharge in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.