# Xero: Users experiencing errors in Xero

- Impact (vendor’s label): none
- Status: resolved
- Started: 2022-03-09 23:12 UTC · Resolved: 2022-03-09 23:12 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.xero.com/incidents/080np13ms5m7](https://status.xero.com/incidents/080np13ms5m7)
- [Company: Xero](https://rewindex.com/company/xero.md)

## Part of an outage event

- [AWS outage, Mar 9, 2022: 12 vendors, 12 incidents](https://rewindex.com/events/2022-03-09-aws)
- This incident blames AWS as the cause. (hop 1, posted +1 h 52 min vs the first vendor naming AWS)
- Evidence: “…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.…”

```mermaid
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
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2022-03-09 23:12 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/xero/incidents/080np13ms5m7 · Markdown: https://rewindex.com/company/xero/incidents/080np13ms5m7.md · JSON: https://rewindex.com/api/v1/companies/xero/incidents/080np13ms5m7 · Generated 2026-10-20T01:31:00.442Z