Sometimes while chatting with Claude, the screen suddenly shows an error message like "Something went wrong" and your message fails to send. Based on causes documented in Claude's official support articles (support.claude.com), this guide walks non-developers through the checks to run, in order. Reading and working through it takes about 5-10 minutes.
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
Before you start
You don't need anything special, but two things will make this faster.
- Confirm you're logged into Claude on the web (claude.ai) or in the app.
- Have access to another browser or a private/incognito window if possible — it helps narrow down the cause.
Quick term glossary
- Session — the connection your browser keeps with Claude's servers after you log in. If it drops, you may see a login error.
- Cache — old page data your browser stores to load pages faster. When it's outdated, it can actually cause errors.
- VPN — a tool that routes your internet connection through another location.
- Extension — an add-on installed in your browser (ad blockers, translators, etc.).
- Capacity constraint — when too many users are active at once and the server can't process every request immediately.
- Incident — a service disruption officially confirmed by Anthropic.
Why does this error appear?
The "Something went wrong" error isn't caused by just one thing — it can appear in any of the situations in the table below. Claude's official support documentation lists VPN use, active browser extensions, and stale cached data as causes of login errors, and describes a separate response error message: "Due to unexpected capacity constraints, Claude is unable to respond to your message. Please try again soon."
| Cause | What's happening | How to check / fix |
|---|---|---|
| Temporary server capacity constraint | Too many users at once; the server can't process every request (normal load management) | Wait a few minutes and retry |
| Service incident | An actual technical problem on Anthropic's systems | Check status.claude.com |
| Login/session issue | Using a VPN, or your login session got tangled | Turn off VPN and log in again |
| Browser cache/extension conflict | Stale cached data or an installed extension interferes with the page | Clear cache, test in a private window |
| Network connectivity issue | Unstable Wi-Fi or mobile data connection | Switch connections and retry |
One important note: capacity-constraint errors don't show up on status.claude.com. According to Claude's official documentation, this is because it reflects normal load management, not an actual technical incident — so you can hit this error even when the status page reads "operational."
Step-by-step fix
Try each step in order below. Each one includes a "you'll know it worked when" signal.
- Resend the message or reload the page. Success signal: if a reply comes through with no error, it was a temporary glitch.
- If you're using a VPN, turn it off and reconnect. Success signal: the login or chat screen loads normally.
- Disable browser extensions temporarily, or open a private/incognito window. Success signal: if it works fine in a private window, an extension was the cause.
- Clear your browser's cache and cookies, then log in again. Menu names vary by browser, so look in settings for "clear cache" or "clear browsing data." Success signal: login and your conversation list load normally.
- Check status.claude.com for a current incident. Success signal: "All Systems Operational" suggests the issue is on your end; a yellow, orange, or red indicator means it's on Anthropic's side.
Common sticking points
A few parts of this checklist tend to trip people up.
- Clearing cache also logged me out — that's expected. Clearing cache and cookies also clears your login session, so you'll need to log back in with your email/password or connected account (like Google) afterward.
- You see a message-length error instead — if the message says your message exceeds the length limit for the conversation rather than "Something went wrong," the cause is different: trim attachments or start a new conversation.
- status.claude.com looks fine but the error persists — it may be a cause that doesn't appear on the status page, like a capacity constraint. Wait a bit and retry, or re-run steps 1-4 above.
How to read status.claude.com
status.claude.com is Anthropic's official page for the current status of claude.ai, the Claude API, Claude Code, and other services. The summary at the top of the page tells you the overall status at a glance: green means operational, while yellow, orange, and red indicate degraded performance, a partial outage, or a major outage, respectively. The page also keeps a history of past incidents, which is useful for checking whether a similar error has happened before.
If nothing above works
If you've tried all five steps and the error keeps happening, the next step is to contact support through the Help menu on Claude's screen. Include the exact error wording, your device and browser (or app version), and the steps that reproduce the error — this speeds up the response. Note that this guide covers errors in the web/app chat interface specifically; errors that come up while integrating with the API directly have different causes and fixes, which is a separate topic.
Frequently asked questions
Q. The same error keeps appearing even after reloading. What now?
Check for an active VPN, disable extensions, and clear your cache, in that order; if it still happens, check status.claude.com for an incident.
Q. status.claude.com shows everything is operational, so why am I still getting errors?
Capacity-constraint errors reflect normal load management rather than a technical incident, so they don't show up on the status page. Waiting a bit and retrying usually resolves it.
Q. What if the error only happens in one specific conversation?
That conversation may have hit its length limit. Try trimming attachments or starting a new conversation.
Q. What if I can't log in at all?
According to official documentation, VPN use, browser extensions, and stale cache are the main causes of login errors. Turn each off or clear it, one at a time, and try again.
Related articles
- Troubleshooting Claude Error Messages: Limits, Capacity, Login
- Fix "Your Previous Message Wasn't Sent" in Claude — Causes & Steps (2026)
- Claude "Your previous response is still processing" error: cause and fix
- Claude Not Working? Fix Login, Access & Errors (2026)
- Claude File Upload FAQ: Formats, 500MB/20-file Limits, PDF Handling
- Claude "An Error Occurred" Message: Causes and Step-by-Step Fixes