Skip to content
Back to SpendeskIncident Postmortem
Spendesk logo

Spendesk

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Spendesk: vendor-reported critical incident on September 29 (tracked 3d 0h)

Sep 29, 04:00 PM → Oct 2, 04:04 PM · 3d 0h · high

Spendesk 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 this incident for 3d 0h, closing it on 2026-10-02T16:04:07.079Z.

Duration
3d 0h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, and therefore cannot describe what users experienced. The incident is known from Spendesk's own status page, which reported a critical outage.

Incident timeline

  1. Sep 29, 04:00 PM

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

  2. Sep 29, 04:00 PM

    Status updated: possible issue

  3. Oct 2, 04:04 PM

    PulseWatch closed the incident

Official updates

  1. Sep 29, 04:00 PM

    Spendesk 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