QuickBooks Online Down or Slow? First Checks and Next Steps
QuickBooks Online outages and slowdowns disrupt tax and bookkeeping work. Learn how to check service status, rule out local issues, and keep working.
When QuickBooks Online becomes slow or unreachable, a single stuck screen can stall tax return prep, payroll, and client bookkeeping. The steps below separate a possible Intuit service issue from a local browser or network problem and give you a safe way to keep working while you wait.
Is the problem on Intuit’s side?
Start with the QuickBooks Online service status page. Look for any listed incident, degradation, or maintenance for your region. If you see a widespread issue, avoid repeated sign-in attempts. Retrying every few minutes can keep the session stuck and make the outage feel longer.
Rule out local issues
If the status page shows no problem, test from a private or incognito window. That step bypasses most extensions and stored data. Then clear the browser cache and cookies for QuickBooks Online, close the browser, and sign in again in a fresh window.
A slow upload connection or a VPN can make QuickBooks Online feel broken even when the service is fine. If your firm allows it, disconnect a non-essential VPN long enough to test. Check that your browser is up to date and that no security extension is blocking scripts from Intuit.
Keep client work moving while you wait
If a payment, tax form, or report area is unavailable, switch to another module or the QuickBooks Online mobile app. For entries that cannot reach the server, keep a simple spreadsheet log of date, payee, account, and amount. When the service returns, enter those transactions once and check the ending balance.
Look for a wider pattern before changing settings
If the problem appears with one browser but not another, the cause is usually local. Disable extensions one at a time and retest after each change. If the problem hits every browser on the same network, test QuickBooks Online on a mobile hotspot to see whether the route or local firewall is at fault.
When the status page shows a current incident, let the service recover before you retry, and keep the spreadsheet log in the meantime. If the status page stays clear, a fresh browser session with extensions disabled is the fastest next test.