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 - UK VAT & MTD and Tax Reporting - BAS, TPAR; the vendor is identified the cause. 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 - UK VAT & MTD, Tax Reporting - BAS, TPAR, AU Payroll

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started27 h 47 min
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 change4 h 32 min

Evidence

  • Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
  • Vendor stage: identified the cause on “UK: CIS - Error when verifying CIS contractors”. 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 “identified the cause”. 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

UK: CIS - Error when verifying CIS contractors

minor identified · started

3 updates

  1. investigating

    We are aware UK customers trying to verify CIS contractors are receiving an error message. This is due to an error with HMRC's services and we've reached out to HMRC asking them to investigate.

  2. identified

    HMRC have confirmed there are currently known issues with the CIS verification service and you can find more information on their website https://www.gov.uk/government/publications/construction-industry-scheme-service-availability-and-issues/construction-industry-scheme-cis-service-availability-and-issues

  3. identified

    HMRC are continuing to investigate the issue they're experiencing with CIS verification - You can find more information on their <a href="https://www.gov.uk/government/publications/construction-industry-scheme-service-availability-and-issues/construction-industry-scheme-cis-service-availability-and-issues">availability page</a>. To verify a sub contractor in the mean time you can <a href="https://www.gov.uk/use-construction-industry-scheme-online">sign in to the Construction Industry Scheme (CIS) online service</a> or call the HMRC CIS Helpline at 0300 200 3210 if you cannot use the online service (limited to verifying up to 10 subcontractors per call).

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