Skip to content
Back to XeroIncident Postmortem
Xero logo

Xero

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Xero: vendor-reported critical incident on September 28 (tracked 1h 25m)

Sep 28, 08:46 PM → Sep 28, 10:11 PM · 1h 25m · high

Xero 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 1h 25m, from Mon, 28 Sep 2026 20:46:09 GMT to Mon, 28 Sep 2026 22:11:37 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
1h 25m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 28, 08:46 PM

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

  2. Sep 28, 08:46 PM

    Status updated: possible issue

  3. Sep 28, 10:11 PM

    PulseWatch closed the incident

Official updates

  1. Sep 28, 08:46 PM

    Xero 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: fallback