Skip to content
Back to RechargeIncident Postmortem
Recharge logo

Recharge

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Recharge: vendor-reported critical incident on September 25 (tracked 3h 0m)

Sep 25, 06:51 PM → Sep 25, 09:51 PM · 3h 0m · high

Recharge reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3h 0m, from Fri, 25 Sep 2026 18:51:07 GMT to Fri, 25 Sep 2026 21:51:08 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
3h 0m
tracked by PulseWatch

Impact

The Recharge service experienced a high-severity disruption for approximately 3 hours. During this period, the service may have been unavailable or experienced degraded performance. This incident was identified through automated monitoring and the vendor's status page. No user-reported data was collected for this incident.

Incident timeline

  1. Sep 25, 06:51 PM

    The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 25, 06:51 PM

    Status updated: possible issue

  3. Sep 25, 09:51 PM

    PulseWatch closed the incident

Official updates

  1. Sep 25, 06:51 PM

    Recharge reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash