ReCharge status history
Current state: operational — “All Systems Operational” per https://status.rechargepayments.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do ReCharge incidents last?
From 24 incidents with a vendor-posted start and resolve time. Longest on record: Missing Data in Email Analytics — 4.2 days (2025-10-23 13:42 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (24)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-01 17:35 UTC | Potential SMS Delays | resolved | none | 39 min |
| 2026-08-07 14:07 UTC | Upcoming Charge Notification Delay | resolved | critical | 11 h 12 min |
| 2026-07-20 18:54 UTC | Merchant Admin Access Degraded | resolved | critical | 1 h 21 min |
| 2026-06-29 14:14 UTC | Delayed analytics data | resolved | minor | 4 h 25 min |
| 2026-04-29 15:05 UTC | Third party provider webhook issue | resolved | minor | 6 h 31 min |
| 2026-04-23 16:14 UTC | Merchant Admin Access Degraded | resolved | major | 46 min |
| 2026-04-07 10:59 UTC | Analytics daily refresh failed impacting data exports. | resolved | minor | 4 h 02 min |
| 2026-02-12 14:59 UTC | Renew Rate Dashboard Error | resolved | minor | 18 min |
| 2025-12-17 17:21 UTC | Degraded Admin Accessibility | resolved | none | 1 h 02 min |
| 2025-12-16 22:11 UTC | API degradation across several services | resolved | critical | 1 h 32 min |
| 2025-11-09 18:06 UTC | Issue with charge processing | resolved | critical | 3 d 6 h |
| 2025-11-04 21:25 UTC | Email Domain Authentication Issues | resolved | minor | 42 min |
| 2025-10-23 13:42 UTC | Missing Data in Email Analytics | resolved | minor | 4 d 5 h |
| 2025-10-20 13:38 UTC | Analytics Data Delayed for 10/19/25 | resolved | minor | 8 h 26 min |
| 2025-10-16 20:25 UTC | Internal Server Error in the onboarding checklist | resolved | none | 1 h 29 min |
| 2025-10-10 12:09 UTC | Analytics daily run data is impacted and not refreshed properly | resolved | none | 1 h 36 min |
| 2025-10-09 10:40 UTC | Analytic drill-down data is unavailable | resolved | none | 4 h 09 min |
| 2025-09-29 21:37 UTC | Internal Server Error in the onboarding checklist | resolved | none | 1 h 32 min |
| 2025-09-26 20:57 UTC | Delayed processing of some Rewards flows | resolved | minor | 3 d 15 h |
| 2025-09-25 12:07 UTC | Stale Analytics Data | resolved | minor | 3 h 42 min |
| 2025-09-18 14:49 UTC | Stale data for 9/17/25 on some analytics dashboards | resolved | minor | 4 h 47 min |
| 2025-09-10 21:00 UTC | Merchant Admin Outage | resolved | critical | 52 min |
| 2025-09-03 17:35 UTC | Shipping Rate Issues | resolved | minor | 47 h 29 min |
| 2025-08-18 08:10 UTC | Getting timeouts (504 status) from the merchant and customer portal UI | resolved | major | 12 h 41 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch ReCharge with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"recharge"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}