Rewindex

CompaniesXeroIncidents

Xero: Global: Xero - Customers should now be able to log in and navigate through Xero as expected

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

AWS outage, Jul 30, 2024 · 12 vendors, 12 incidents

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

“…nk customers for their patience during this time. This was caused by an issue relating to AWS, one of Xero's third-party providers. We apologise for the inconvenience.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSXero, Substack, Mapbox1 to 4 hours later3 vendors, 2 blamed AWSSegment, Hootsuite, HoneycombLater1 vendor, 1 blamed AWSHeapXero (this incident)posted +0 min
AWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSXero, Substack, Mapbox1 to 4 hours later3 vendors, 2 blamed AWSSegment, Hootsuite,HoneycombLater1 vendor, 1 blamed AWSHeapXero (this incident)posted +0 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/>3 vendors, 3 blamed AWS<br/>Xero, Substack, Mapbox"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 2 blamed AWS<br/>Segment, Hootsuite, Honeycomb"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Heap"]:::blames
  root --> later
  me["Xero (this incident)<br/>posted +0 min"]:::me
  h1 --- 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 now seeing recovery across our systems. Customers should be able to log in and navigate through Xero as expected. We thank customers for their patience during this time. This was caused by an issue relating to AWS, one of Xero's third-party providers. We apologise for the inconvenience.

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

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