CHYP.ai · ORBIT // Cloudy_Day Security Suite

Business & CRM

Degraded / minor incident Xero status

xero.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Xero's status page shows “Degraded / minor incident” in Tax Reporting - NZ GST and NZ Payroll; the vendor is doing maintenance. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.

confidence: low Vendor: minor issue · users: normal · routing: no data · upstream providers: major.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Tax Reporting - NZ GST, NZ Payroll, Xero Tax (NZ)

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started5 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change20 h 36 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: doing maintenance on “Inland Revenue (NZ) planned maintenance”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • Amazon Web Services reports an issue. Xero may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Xero's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “doing maintenance”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

Xero may run on Amazon Web Services (inferred). We don't map other services that depend on Xero. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Xero or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Xero. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Inland Revenue (NZ) planned maintenance

maintenance in_progress · started

2 updates

  1. scheduled

    The Inland Revenue Department (IRD) is completing planned maintenance from 3pm Saturday 21 November 2026 to 9am Sunday 22 November (NZDT). During this time, customers will be unable to file GST returns, income tax returns or payday filings to IRD from Xero. Please note, you can continue to run and view GST, income tax returns and payruns during this time.

  2. in_progress

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next