Operational QuickBooks Online status
quickbooks.intuit.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
QuickBooks Online looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: United States, EMEA, Canada
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 79 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Some users may encounter issues when trying to Login to QuickBooks Online”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. QuickBooks Online may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside QuickBooks Online'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 “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
QuickBooks Online may run on Amazon Web Services (inferred). We don't map other services that depend on QuickBooks Online. 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 QuickBooks Online 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 QuickBooks Online. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Some users may encounter issues when trying to Login to QuickBooks Online
major resolved · started · resolved
6 updates
- investigating
We're currently investigating an issue affecting QBO logins. Some users may also see errors while using the different features inside the application. Our engineering team is actively working to resolve this, and we'll share updates as they become available. We apologize for the inconvenience.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- identified
Our engineering team has figured out the root cause of the issue and a fix is in deployment, we are already seeing recovery across our systems and soon the service will be fully restored. We'll share updates as they become available. We apologize for the inconvenience this caused and thank you for your patience.
- identified
Our engineering team has figured out the root cause of the issue and a fix is in deployment, we are already seeing recovery across our systems and soon the service will be fully restored. We'll share updates as they become available. We apologize for the inconvenience this caused and thank you for your patience.
- resolved
The issue has been fixed and we confirm the system recovery across all regions. We apologize for the inconvenience this caused and thank you for your patience.
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.