Rewindex

CompaniesXeroIncidents

Xero: Users experiencing errors in Xero

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.xero.com (opens in new tab)
Part of an outage event

AWS outage, Mar 9, 2022 · 12 vendors, 12 incidents

Xero’s incident blames AWS as the cause. (hop 1, posted +1 h 52 min vs the first vendor naming AWS)

“…s experienced errors for a short period of time in the Xero platform due to an issue with Amazon Web Services (AWS). AWS have now resolved this issue and updated their Health Dashboard https://health.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXeroXero (this incident)posted +1 h 52 min
AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSCourier, Unbounce1 to 4 hours later1 vendor, 1 blamed AWSXeroXero (this incident)posted +1 h 52 min
Xero is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>2 vendors, 2 blamed AWS<br/>Courier, Unbounce"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Xero"]:::blames
  root --> h4
  me["Xero (this incident)<br/>posted +1 h 52 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    We are aware that some users experienced errors for a short period of time in the Xero platform due to an issue with Amazon Web Services (AWS). AWS have now resolved this issue and updated their Health Dashboard https://health.aws.amazon.com/health/status

From Xero’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.xero.com (opens in new tab).

Xero profileRecent Xero incidentsMarkdownJSON