Skip to content
Back to WaveIncident Postmortem
Wave logo

Wave

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Wave: vendor-reported critical incident on September 22 (tracked 2h 17m)

Sep 22, 07:15 AM → Sep 22, 09:32 AM · 2h 17m · high

Wave 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 2h 17m, from Tue, 22 Sep 2026 07:15:14 GMT to Tue, 22 Sep 2026 09:32:44 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2h 17m
tracked by PulseWatch

Impact

The Wave service experienced a high-severity disruption for 2 hours and 17 minutes. During this period, the incident was identified through automated monitoring and the vendor's status page. No user-reported data was collected for this incident, and therefore, no specific user-visible features, regions, or issue types were recorded based on user reports.

Incident timeline

  1. Sep 22, 07:15 AM

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

  2. Sep 22, 07:15 AM

    Status updated: possible issue

  3. Sep 22, 09:32 AM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 07:15 AM

    Wave 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