Skip to content

Outage tracker

QuickBooks: incident history

The last 24 hours in detail, QuickBooks's declared incident record, and our regional check results beside it.

← Back to QuickBooks's check readings

We started checking QuickBooks on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when QuickBooks reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is QuickBooks's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what QuickBooks's own status page declared. Below it, any public chatter we saw about QuickBooks and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what QuickBooks's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about QuickBooks in the last 24 hours, which is not evidence that nothing is wrong.
QuickBooks's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is QuickBooks's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention QuickBooks next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.83%582
US-West99.77%436
Europe100.00%398
Asia-Pacific100.00%239

Their declared record

QuickBooks's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Duplicate transactions affecting some Payroll and Payments customersAll systems operational
Sep 16, 2026, 5:30 PM UTC to Sep 16, 2026, 11:02 PM UTC (5h 32m)resolved
their latest update (Sep 16, 2026, 11:02 PM UTC): This issue is resolved. Payroll and Payments customers have been contacted. Refunds of duplicate transactions are being processed. We're sorry for the disruption and appreciate your patience.
Some users may encounter issues when trying to Login to QuickBooks OnlinePartial outage
Sep 2, 2026, 4:16 AM UTC to Sep 2, 2026, 4:19 AM UTC (4 min)resolved
their latest update (Sep 2, 2026, 4:19 AM UTC): 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.
Some QuickBooks users receive errors and are unable to view transactions when searching.Minor incident
Aug 31, 2026, 6:26 PM UTC to Aug 31, 2026, 8:30 PM UTC (2h 4m)resolved
their latest update (Aug 31, 2026, 8:30 PM UTC): The search issues affecting QuickBooks have been resolved. We're continuing to monitor for full recovery. Thank you for your patience
Quickbooks Online Latency IssuePartial outage
Aug 19, 2026, 2:30 PM UTC to Aug 19, 2026, 4:54 PM UTC (2h 23m)resolved
their latest update (Aug 19, 2026, 4:54 PM UTC): Earlier today, some users experienced issues with QuickBooks Online (QBO) features. Our teams have identified and resolved the underlying problem. All services are now restored and functioning normally. We appreciate your understanding and patience.
HMRC service interruption affecting some Making Tax Digital (MTD) for Income Tax submissions in QuickBooks OnlineMinor incident
Aug 5, 2026, 1:20 PM UTC to Aug 5, 2026, 5:46 PM UTC (4h 26m)resolved
their latest update (Aug 5, 2026, 5:46 PM UTC): HMRC service interruption We're currently experiencing connection issues that may affect some MTD for Income Tax submissions. You may notice: Incorrect tax period dates listed on your obligations, causing HMRC to reject submissions A repeated "reauthorise with HMRC" request tha…
QuickBooks Online Login IssuePartial outage
Jul 8, 2026, 1:08 PM UTC to Jul 8, 2026, 4:25 PM UTC (3h 17m)resolved
their latest update (Jul 8, 2026, 4:25 PM UTC): This incident has been resolved.
Resolved - Unable to Save TransactionsAll systems operational
Jun 18, 2026, 6:09 PM UTC to Jun 18, 2026, 6:09 PM UTC (0 min)resolved
their latest update (Jun 18, 2026, 6:09 PM UTC): We have resolved the issue affecting users' ability to save invoices and transactions. Some users were experiencing an error related to sales tax when attempting to save. We apologize for any inconvenience this may have caused.
QuickBooks Desktop Payroll updates returning Internet connection errorMinor incident
Jun 15, 2026, 2:54 PM UTC to Jun 15, 2026, 6:18 PM UTC (3h 24m)resolved
their latest update (Jun 15, 2026, 6:18 PM UTC): Our teams have identified and resolved the underlying problem. All services are now restored and functioning normally. We appreciate your understanding and patience.
QuickBooks Online Payroll - Intermittent IssueMinor incident
May 12, 2026, 7:49 PM UTC to May 12, 2026, 9:00 PM UTC (1h 11m)resolved
their latest update (May 12, 2026, 9:00 PM UTC): Our teams have resolved the issue, and users should now be able to run through QuickBooks Payroll functions. Thank you for your patience as we worked to resolve this issue.
Unable to access Expense Transactions menuAll systems operational
Apr 27, 2026, 2:50 PM UTC to Apr 27, 2026, 4:21 PM UTC (1h 30m)resolved
their latest update (Apr 27, 2026, 4:21 PM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents QuickBooks has declared in the history we hold.

These entries are QuickBooks's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

QuickBooks's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.