Sometimes Claude suddenly stops responding, won't log in, or shows an error. The causes fall into four buckets — (1) temporary server/capacity issues, (2) your browser/network/login, (3) usage limits, and (4) answer quality (hallucination). Here's what to check first, by symptom.
First: is it just you, or a full outage?
Start by checking whether it's a service-wide outage. The official status page status.claude.com shows real-time incident status, scope, and recovery. Claude does occasionally have global outages (for example, a large one on June 2, 2026); during those, there's nothing you can do but wait for recovery.
However, the message "Due to unexpected capacity constraints, Claude is unable to respond" is not an outage. Officially, this means the system is working normally but demand is high; it usually clears on its own shortly. Capacity issues don't appear on the status page, so just try again in a few minutes.
When you can't log in
- No verification email: check spam/promotions, then try resending. Work/school mail may block external senders — try a personal address.
- Credentials are right but login fails: clear your browser cache and cookies and retry.
- Still stuck: open an incognito window → disable ad/script-blocking extensions → update your browser → try a different browser. It may also be a network issue (corporate firewall/VPN).
When there's no response or it stalls
- "Capacity" message: high demand, as above — retry in a few minutes.
- Slows down in a long chat: Claude re-reads the whole conversation each turn, so very long chats can slow down or hit length limits. Start a new conversation.
- A tool hangs: turn off heavy features (web search, Research, MCP connectors) and retry.
When you hit a usage limit
A "you've reached your limit" notice isn't an error — it's expected. Session usage limits reset about every 5 hours. See the usage limits guide for how limits work and how to reduce usage.
When answers are wrong, or it claims to have sent a link/email
This isn't a connection error — it's hallucination. Claude can answer as if it accessed a link or sent an email even when it can't (when that tool isn't connected). Official docs cover this. What to do:
- Verify important facts, figures, and links at the original source.
- Write clearer, more specific prompts with enough context (see prompting guide).
- Ask whether it can actually access/send something, and tell it to say so when it can't.
When Claude Code won't work (developers)
- Install/login fails: update the client and re-authenticate (run
claude→ browser login). If OAuth is blocked, you can bypass it with theANTHROPIC_API_KEYenv var. - Region limits: if the installer returns 403 or "App unavailable in region," your country may not be supported.
- For detailed diagnostics, see the install/troubleshooting pages at code.claude.com/docs.
If nothing works
If none of the above helps, visit the official help center support.claude.com for troubleshooting articles or to contact support. If you suspect a full outage, watch status.claude.com and wait for recovery.