When Claude isn't working, the exact words on screen tell you why: it's a usage limit, a length limit, a login error, a capacity constraint or a real service outage, and each one has a different fix. As of October 2026 Anthropic's own troubleshooting guide splits problems into exactly those five, so read the message before you refresh or log out.
The catch: capacity constraints aren't an outage
This is the message that sends most people to search. It reads: 'Due to unexpected capacity constraints, Claude is unable to respond to your message. Please try again soon.' It feels like Claude is down. Anthropic says it isn't.
That message means demand is high across all users and the system is working normally while it manages the load. It clears as demand shifts, usually within a few minutes. And here's the part nobody guesses: capacity constraints won't appear on the status page, because they aren't incidents. So if you see that message, check status.claude.com, find everything green and decide the status page is wrong, it isn't. You're just in a busy patch. Wait a few minutes and send again.
Match the message to the cause
Here's how the messages map to causes and fixes, based on Anthropic's troubleshooting article as of October 2026.
| What you see | What it means | What to do |
|---|---|---|
| 5-hour limit reached / weekly limit reached | Plan usage limit | Wait for the reset time shown, or use usage credits |
| Now using credits | Limit hit, credits covering it | Nothing to fix; check monthly spend limit |
| Your message will exceed the length limit | Message or files too long | Split, summarise, or start a new chat |
| There was an error logging you in | Login error | No VPN, disable extensions, clear cache and cookies |
| Due to unexpected capacity constraints | High demand, not an outage | Try again in a few minutes |
| Nothing loads for anyone | Service incident | Check status.claude.com |
Usage limit messages
Your plan has two clocks running: a five-hour session limit and a weekly limit. Some plans also have an additional weekly limit that applies only to Fable, so you can be stopped on Fable while other models still answer.
Claude warns you before you hit either one. The warnings read 'Approaching session limit' or 'Approaching weekly limit', sometimes with a figure for how much you've used. If you reach the limit and you don't have usage credits, you'll see either '5-hour limit reached - resets' followed by a time, or 'You've reached your weekly limit. It resets' followed by a day and time.
Nothing is broken in either case. The fix is to wait for the reset time Claude shows you, or turn on usage credits if you're on a paid plan. If you keep hitting these, my guide to how Claude's usage limits work by plan explains where each plan runs out.
When it says you're on credits
With usage credits enabled in Usage settings on a paid plan, reaching a session or weekly limit doesn't stop you. Your requests switch to pay-as-you-go on credits, and they keep going until you reach your monthly spend limit or your credit balance runs out with auto-reload off.
The messages here are '5-hour limit resets' with a time, followed by 'continuing with usage credits', or simply 'Now using credits'. The confusing bit, as Anthropic points out, is that the approaching-limit warning may still show at the moment of the switch. That can look like Claude cut you off when your work is still carrying on. Nothing needs fixing, but it's worth checking your monthly spend limit so the credits don't run further than you meant.
The length limit error
This one reads: 'Your message will exceed the length limit for this chat. Try attaching fewer or smaller files or starting a new conversation.' It means the message is too long, usually because of big attachments or a very long chat.
On paid plans with code execution enabled, Claude summarises earlier messages automatically, so you shouldn't see it often. When you do, Anthropic lists four fixes:
- Break the content into smaller chunks.
- Summarise or extract the key sections first.
- Ask Claude to identify the relevant portions before you send the rest.
- Start a new conversation.
Login errors
For the generic 'There was an error logging you in', Anthropic's checklist is short. Make sure you're not on a VPN, disable any active browser extensions, and clear your browser's cache and cookies. If you still can't get in after that, check status.claude.com for an active incident.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Real outages and the status page
A service incident is different from everything above. Anthropic defines it as a disruption where Claude is unavailable or significantly degraded for all or most users. That's the only kind of problem status.claude.com tracks, with real-time updates on scope, impact and resolution. An incident shows there. Load management, the capacity message, doesn't.
So the status page is a good test. If it shows an incident, there's nothing for you to fix on your side: wait for Anthropic's updates. If it's clear and you're getting the capacity message, give it a few minutes. If it's clear and you're getting a limit, length or login message, the fix is in your hands.
Problems with their own fix
A few errors sit outside those five, and Anthropic gives them their own help articles:
- Output blocked by content filtering policy. That's a separate error with its own article. It isn't a capacity or limit problem, so waiting won't change it.
- Claude in Chrome. The browser extension has its own troubleshooting guide.
- Claude Code. Installation and sign-in problems have a separate article.
- Stretching your plan. There's a 'Usage limit best practices' article and a 'How do usage and length limits work?' article if limits are the recurring problem.
Fix it in this order
- Read the exact message and match it to the table.
- If it names a limit, check the reset time or turn on usage credits.
- If it names length, shorten the message or start a new chat.
- If it's a login error, drop the VPN, disable extensions and clear cache and cookies.
- If it says capacity constraints, wait a few minutes and retry.
- If nothing works for anyone, check status.claude.com.
My verdict
I'd stop treating every Claude hiccup as an outage. Most of the time the message has already told you the answer, and the fix takes a few minutes or a fresh chat. I'd turn on usage credits if limits keep stopping you mid-task and you'd rather pay as you go than wait, and skip them if you're happy to wait for the reset. If limits are hitting you every week, look at whether your plan still fits; the breakdown of every Claude plan lays out the options. The capacity message is the only one where doing nothing is the right fix.
Frequently asked questions
Is Claude down or is it just me?
Check status.claude.com. As of October 2026 a real outage shows there, but the capacity constraints message doesn't, because that's high demand rather than an incident.
What does 'unexpected capacity constraints' mean on Claude?
It means demand is high across all users and Claude is managing load. Anthropic says it usually clears in a few minutes.
Why does Claude say I've reached my limit?
Your plan has a five-hour session limit and a weekly limit. Wait for the reset time shown, or turn on usage credits on a paid plan.
How do I fix the Claude length limit error?
Split the content into smaller chunks, summarise the key sections first, or start a new conversation.
Why can't I log in to Claude?
Turn off any VPN, disable browser extensions and clear your cache and cookies, then check status.claude.com if it still fails.
