Is Help Scout Down? How to Check Status (and What to Do)

Quick answer: how to check if Help Scout is down

The single source of truth is Help Scout's own status page: status.helpscout.com. Don't rely on Downdetector, a tweet, or a colleague's hunch as your first move — go straight to the status page and check the component that matches what's broken for you, because Help Scout reports status per service (the Web App, Beacon, Docs, the APIs, email processing, and more), and a single component can be degraded while everything else runs fine.

The 30-second version:

1. Go to status.helpscout.com. It runs on separate infrastructure, so it stays reachable even when the Help Scout app itself is down.
2. Read the overall banner at the top, then scroll to the individual components — Web App, Beacon, Docs Sites, Inbox API, Email Processing, and so on.
3. Check for any active incidents and scheduled maintenance posted on the page.
4. If it's all green there but broken for you, the problem is probably on your side — jump to "Is it Help Scout, or is it you?" below.

That's it. The rest of this guide is how to read that page properly and what to do next.

How to check Help Scout status authoritatively

Anyone can glance at the top banner, but the useful trick — the one most "is Help Scout down" articles skip — is reading the right component, because Help Scout breaks its service out into separate pieces and an incident is almost always scoped to one of them.

Step 1 — Go to the official Help Scout Status page

The authoritative source is status.helpscout.com. Help Scout deliberately hosts it on independent infrastructure that stays online even during an app outage — so if the Help Scout web app is down, the status page is still the place to look. Help Scout's own uptime documentation confirms this, and notes the platform has run at 99.99% uptime over the trailing 12 months — which is reassuring on a normal day and exactly why a real outage feels so jarring when it happens.

The page is an Atlassian Statuspage (the same hosted status-page product a lot of SaaS vendors use), so if you've read a status page before, the layout will feel familiar: an overall status banner up top, a list of components with colored indicators, an incident feed, and a history of past incidents.

Step 2 — Read the components, not just the banner

This is the part most people miss. The big green "All Systems Operational" banner is a summary — the detail lives in the components below it. Help Scout reports status across roughly a dozen-plus services in two groups, including:

• Web App — the main agent interface where you read and reply to conversations.
• Beacon — the embeddable chat/contact/help widget you put on your website or app.
• Docs Sites — your customer-facing knowledge base.
• Email Processing — the pipeline that turns inbound email into conversations in your Inbox.
• Inbox API and Docs API — the programmatic interfaces your integrations rely on.
• Mobile Apps, Marketing Site, and mailbox functions like counts, folders, reports, and search.
• AI features — Help Scout's AI Answers, AI Assist, AI Drafts, and AI Summarize.

(Aggregators that mirror the page have counted on the order of ~13 components across ~2 groups — treat that as approximate; Help Scout adds and renames components over time, especially around AI.) The granularity is the whole point: if Beacon is degraded but the Web App is operational, your widget is the problem, not your team's inbox — and you can tell customers exactly that. If Email Processing is down, that explains why new emails aren't turning into conversations even though the app itself loads fine.

Step 3 — Read the legend

Help Scout's Statuspage uses four states:

The takeaway: "degraded" is not the same as "down." A degraded component is usually slow or intermittently failing, not fully offline — which changes both your diagnosis and what you tell customers.

Step 4 — Check for scheduled maintenance

Not every disruption is an "outage." Help Scout posts scheduled maintenance (for example, planned database maintenance windows) to the same status page ahead of time, and it shows as its own state. If features behave oddly at an oddly specific time, check whether a maintenance window is posted before you escalate — planned maintenance is expected behavior, not a fault.

Step 5 — Subscribe so you're told next time

Rather than refreshing the page, subscribe. Click the Subscribe button in the top-right corner of the status page and pick your channel: email, SMS (text message), or webhook. Help Scout also publishes RSS and Atom feeds if you'd rather pipe incidents into a reader or a team channel. Now incidents come to you instead of you hunting for them — and you hear about them from Help Scout before a customer tells you.

Is it Help Scout, or is it you?

Half of "is Help Scout down" panics turn out to be local. Before you tell customers Help Scout is broken, run this elimination ladder in order — it goes from fastest to most thorough.

1. Check the status page first (above). If the component that matches your symptom is all operational, lean toward a problem on your end.
2. Isolate the component. Help Scout is several services, so figure out which is broken. Can you load the Web App but Beacon is dead on your site? Can your team reply, but inbound email isn't turning into conversations? Is only Docs down? Narrowing to one component tells you whether this is even a Help Scout-shaped problem.
3. Test from another network and device. Open Help Scout on mobile data instead of office Wi-Fi, or from a phone instead of a laptop. If it works on cellular but not on the corporate network, the issue is your network/firewall, not Help Scout.
4. Try an incognito/private window — or a different browser. If incognito works, a browser extension, a corrupted cache, or a stale session is the culprit, not the platform. Clearing your cache or disabling extensions one at a time usually resolves it.
5. For inbound email, check your forwarding and DNS. Help Scout receives a lot of mail by forwarding from your own mailbox (or via a custom domain). If new emails aren't arriving as conversations but the app is otherwise fine, the fault may be in your email forwarding rule, your MX/DNS records, or your provider's spam filtering — not in Help Scout. One quiet channel with everything else operational usually points here.
6. Corroborate with third-party trackers. Sites like Downdetector, IsDown, or StatusGator aggregate user reports and mirror Help Scout's components. A spike there alongside a degraded/down component on the official page is strong confirmation of a real outage. Treat them as corroboration only — they're crowd-sourced, not authoritative. The official Help Scout status page is the source of truth.

The pattern to internalize: everything broken + a down component on the status page = Help Scout. One thing broken + all operational = you (or your network, browser, or email setup).

What to do during a real Help Scout outage

Status page confirms it — a component is degraded or down. Now manage it. The goal is to protect the customer experience and your own sanity, not to "fix" something you can't fix.

• Subscribe to updates first. Get on the incident's notifications (email, SMS, or webhook) so you're not refreshing a page. Help Scout posts progress on the incident itself.
• Set customer expectations proactively. Post a banner on your Docs site or website, set an away message on Beacon, and tell customers you're aware and waiting on your provider. A short, honest "we're experiencing a temporary outage with our support system" beats silence.
• Don't thrash your settings. The instinct to "fix" it by toggling workflows, reinstalling Beacon, or rewiring email forwarding during an outage usually creates a second mess to clean up once Help Scout recovers. If the status page says it's Help Scout, leave your configuration alone.
• Capture work out-of-band. If conversations aren't loading, log incoming issues somewhere temporary (a shared doc or spreadsheet) so nothing is lost, and reconcile once service returns. Inbound email is usually queued and delivered once Email Processing recovers, but a manual log is cheap insurance.
• Have a fallback channel. Know in advance where customers go if Help Scout is unreachable — a status page of your own, a social account, or a simple email inbox. Decide this before you need it.
• Wait for "resolved," then verify. When the incident is marked resolved, do a quick end-to-end test (send a test email, check it becomes a conversation, load Beacon, post a reply) before announcing the all-clear.

If you're stuck and Help Scout is genuinely broken for you but no incident is posted, the documented move is to email Help Scout support at [email protected] — that's the path their uptime docs point you to when the status page is quiet but you're still having trouble.

How to prevent the next scramble

You can't prevent Help Scout outages, but you can make them boring instead of chaotic.

• Subscribe to status notifications so you hear it from Help Scout before a customer tells you.
• Bookmark the status page and make it the team's first reflex, ahead of guessing.
• Write a one-page outage runbook: who posts the customer banner, where you log conversations, which fallback channel you use, who owns the all-clear. Five minutes now saves an hour later.
• Know your component map. Understand which parts of your support stack ride on which Help Scout component — Beacon on your site, Docs for self-serve, Email Processing for inbound, the APIs for integrations — so an incident note instantly tells you what will and won't work.
• Map your dependencies. Anything that sits on top of Help Scout — integrations, automations, AI features — depends on Help Scout being up. Knowing that chain ahead of time tells you instantly what's affected during an incident.

Where AI fits in during an outage

If you run an AI agent layer on top of your helpdesk, it's worth being honest about what that means during an outage. An AI agent that reads and resolves tickets does so through the helpdesk's platform — so if the helpdesk itself is down, the dependent layer is affected too. An AI agent can't read or update conversations that the platform can't serve. An AI layer makes your support faster on a normal day; it does not replace the helpdesk or keep it running when the platform is offline.

A quick, honest note on tooling fit: Macha is an AI agent layer that works on top of an existing helpdesk — but today it connects to Zendesk and Freshdesk only, not Help Scout. So if you're on Help Scout, Macha isn't a drop-in for you right now; the relevant reading here is purely the outage playbook above. (If you happen to run Zendesk elsewhere in your stack, Macha on Zendesk shows how the AI-layer model works.) Where that kind of AI layer earns its keep is every other day: deflecting and resolving repetitive tickets so your queue is smaller — which, incidentally, means less of a backlog to dig out of once an outage clears. If and when it fits your stack, you can try it free — 7-day free trial, no credit card required.

Frequently asked questions

Is Help Scout down right now? Check the authoritative source: go to status.helpscout.com, read the overall banner, then scroll to the individual components (Web App, Beacon, Docs, Email Processing, the APIs) to see which one matches your symptom. Operational means it's running normally; degraded means partial disruption; outage means it's down. The status page runs on separate infrastructure, so it stays reachable even if the Help Scout app itself is offline.

What is the Help Scout status page URL? status.helpscout.com. It's an Atlassian Statuspage that shows real-time component status, active incidents, scheduled maintenance, and incident history, and it's hosted independently so it stays up during app outages.

Why does Help Scout work for other companies but not for us? Most likely a problem on your end. Help Scout runs a single global service (it doesn't split status by region), so if the status page shows all components operational, the issue is probably local. Isolate the broken component, test from another network and device, try an incognito window, clear your cache or disable extensions, and — for missing inbound email — check your forwarding rules and DNS before concluding it's Help Scout.

How do I get notified about Help Scout outages? Click the Subscribe button in the top-right corner of status.helpscout.com and choose email, SMS (text), or webhook. Help Scout also offers RSS and Atom feeds if you'd rather pull updates into a reader or team channel.

What's the difference between "degraded" and "outage"? Help Scout's status page uses four states: operational (up), degraded (warn) — partial or intermittent disruption where things are slow or flaky but largely working, outage (down) — the component is currently unavailable, and maintenance — a planned window. So "degraded" is not the same as "down."

The status page is all operational but Help Scout is broken for me — what now? That points to a local issue. Isolate which component is failing, test from a different network and device, open Help Scout in an incognito window or another browser, clear your cache, and (for inbound email) check your forwarding and DNS. If everything points to Help Scout but no incident is posted, email Help Scout support at [email protected].

Can I trust Downdetector to tell me if Help Scout is down? Use it as corroboration, not as the answer. Downdetector, IsDown, and StatusGator aggregate user reports and mirror Help Scout's components, which helps spot a widespread problem fast — but they're crowd-sourced. Confirm against the official status.helpscout.com for the specific component you care about.

The bottom line

When you're asking "is Help Scout down?", skip the guesswork and go to status.helpscout.com — then read the component that matches what's broken, not just the top banner, because Help Scout reports status per service and an incident is usually scoped to one piece (Beacon, Email Processing, Docs, an API) rather than the whole platform. Read the legend (operational, degraded, outage, maintenance), check for scheduled maintenance, and subscribe so the next incident finds you instead of the other way around. If everything's operational but things are still broken, work the elimination ladder — isolate the component, try another network, an incognito window, your email forwarding and DNS — because half the time it's not Help Scout at all. And during a real outage, the move is to communicate early, leave your settings alone, and wait for the official "resolved." For background on the platform itself, see what Help Scout is and a rundown of Help Scout's features.

Status infrastructure, components, legend, uptime figure, and subscription behavior verified against Help Scout's status page and official uptime documentation, June 2026. Help Scout updates its products, components, and UI periodically — confirm exact labels in your own status view. Component and group counts cited from a third-party mirror and flagged approximate.