Claude's "An error occurred" message on the web app (claude.ai) or mobile app usually isn't a sign that your account is suspended or broken — it's a generic, temporary communication error. Working through the likely causes in order, from server-side issues down to your browser and network, resolves most cases within 5 to 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 to follow these checks. Just make sure you have:
- An account you can log into on Claude's web app (claude.ai) or mobile app
- A way to switch your internet connection (e.g., Wi-Fi to mobile data)
- (Optional) A different browser, or a private/incognito window
Quick term glossary
These terms come up in the steps below, so it helps to know them first.
- Session — the temporary connection data that keeps you logged in. Leaving a tab open too long can let it expire, which triggers errors.
- Extension — a browser add-on, like an ad blocker or translator. Some extensions conflict with a site's scripts and cause errors.
- Cache — data your browser stores temporarily to load pages faster. An old or corrupted cache can also cause errors.
- Status page — a page where a service provider publishes real-time system status. For Claude, that's status.anthropic.com.
Why does "An error occurred" show up?
This message doesn't point to one specific cause — it's a generic error that shows up in four common situations: temporary server load, a session issue, a browser extension conflict, or network instability.
The table below summarizes common signs and the first fix to try for each cause.
| Cause | Common sign | First thing to try |
|---|---|---|
| Temporary server load | Multiple people hit the same error at once; it clears up on its own shortly after | Check status.anthropic.com, then wait a bit |
| Session issue | Happens after a tab has been open a long time, or after logging in elsewhere | Log out and back in, or refresh the page |
| Extension conflict | Only happens in one browser; other sites also behave oddly | Try an incognito window, or disable extensions temporarily |
| Network instability | Messages cut off mid-response, or responses stay slow | Toggle Wi-Fi/VPN off and on, or switch networks |
Step-by-step fix
Working through these steps in order is the fastest way to narrow down the cause.
- Check the status page — go to status.anthropic.com and check the status for claude.ai, the Claude API, Claude Code, and other components. Success looks like: everything shows as operational, which means the issue isn't on Anthropic's end — move to the next step. If something shows an outage, wait until it clears.
- Refresh and log back in — refresh the page, and if that doesn't help, log out and log back in. Success looks like: the conversation view loads normally and you can type a message again.
- Check incognito mode and extensions — open a private/incognito window and see if the error still happens there. If it doesn't, turn off extensions like ad blockers one at a time to find the culprit. Success looks like: with extensions off or in incognito mode, your message sends without an error.
- Check your network — turn Wi-Fi off and back on, or turn off a VPN if you're using one. If possible, try a different network, such as mobile data. Success looks like: after switching networks, the response comes through completely without an error.
- Try a new conversation — if none of the above works, start a new conversation and resend the same message. Success looks like: the new conversation responds normally, which suggests the old conversation itself had an issue.
Common sticking points
Most cases resolve with the five steps above, but a few situations need extra attention.
- The error only happens in one specific conversation — if a new conversation works fine but an existing one keeps failing, that conversation is likely too long or corrupted. Copy anything important, then continue in a new conversation.
- Even the logout button doesn't respond — clear your browser's cache and cookies, then try again. If that still doesn't work, check whether you can log in from a different device or browser to tell whether the issue is with your account or your device.
- A usage-limit or capacity message appears instead — if what you're actually seeing is a usage-limit or capacity notice rather than "An error occurred," the cause is different. See the related guide below.
Frequently asked questions
Q. Does "An error occurred" mean my account has been suspended?
No. This message is unrelated to your account status — it's a generic error from the communication process, and it resolves with the steps above in most cases.
Q. What if the same error keeps happening after several retries?
If the status page shows no outage, try starting a new conversation and switching networks at the same time. If it still persists, try a different device to narrow down whether the issue is with your account or your device.
Q. Is this the same as the 529 overload error?
No. A 529 error specifically indicates server overload, while "An error occurred" is a generic message that doesn't specify a cause. See the related guide below for how to handle 529 errors.
Q. Does this happen on the mobile app too?
Yes, it can appear on both the web app and mobile app, and the causes to check (server, session, network) are the same. The extension-related cause doesn't apply on mobile, though.
Related guides
These related error guides cover similar situations.