Skip to content

A troubleshooting guide

Is Claude Code down, or is it you?

Two things settle it in about a minute: Anthropic’s status page, and the exact words of the error Claude Code shows you. Here is where to look, and what each error means, from Claude Code’s error reference.

Check in a minute

1

Look at Anthropic's status page

status.claude.com is where Anthropic posts outages. The two rows that matter for Claude Code are “Claude Code” and “Claude API (api.anthropic.com)”. If either shows an incident, it’s them, and waiting is the fix.

2

Read the error's exact words

Claude Code names the cause in the error itself. A server error or “overloaded” is Anthropic’s side; a limit, a login or “unable to connect” is yours. The table below sorts each one.

3

Test the connection from your shell

Run curl -I https://api.anthropic.com in the same terminal. Any HTTP response means your Mac can reach the API; a timeout or “could not resolve host” points at your network, VPN or proxy.

The error says whose side it’s on

Claude Code already retries server errors, overloads and timeouts before it shows you anything, so a short blip never reaches you. What does reach you sorts into three kinds.

API Error: 500 Internal server errorWhose side: Anthropic'sA failure inside the API, not your prompt, settings or account. Wait a minute and send again; for a long prompt, type “try again” rather than pasting it back.
API Error: Repeated 529 Overloaded errorsWhose side: Anthropic'sThe API is at capacity for everyone. It isn’t your usage limit and doesn’t count against it. Capacity is per model, so /model to switch often gets you going again.
API Error: Server is temporarily limiting requests (not your usage limit)Whose side: Anthropic'sAnthropic is slowing requests down for a while. Wait briefly and retry.
API Error: Server error mid-responseWhose side: Anthropic'sIt failed partway through an answer. Claude Code keeps what arrived rather than resend and risk running tools twice: reply continue.
You've hit your session limit · resets 3:45pmWhose side: YoursYour plan’s allowance is used up, so nothing is down. The weekly limit reads the same way. Wait for the reset it names, or run /usage to see your limits.
Not logged in · Please run /loginWhose side: YoursAlso “OAuth token revoked” and “Login expired”. Your sign-in lapsed: run /login.
Unable to connect to APIWhose side: YoursAlso “Can’t reach the API server” (ENOTFOUND) and “Connection refused”. Usually no internet, a VPN blocking api.anthropic.com, or a proxy that isn’t set. If curl works, check for a leftover ANTHROPIC_BASE_URL pointing at a proxy that’s gone.
API Error: Request rejected (429)Whose side: Could be eitherThe rate limit on your API key or cloud project. Run /status to see which credential is active: a stray ANTHROPIC_API_KEY can override your subscription.
Request timed outWhose side: Could be eitherRetry. If it keeps happening and the status page is clear, treat it as your network or a proxy holding responses back.

Status page clear and the error keeps coming? Run /doctor inside Claude Code for a check of your installation and settings, and /feedback to report it to Anthropic.

Or let the menu bar check for you

Hear about an outage before you start debugging

Perch reads status.claude.com for you once you’ve used Claude Code on your Mac: often while a session is open, less often between them. When the Claude Code or Claude API row shows an outage, a red banner in the menu bar dropdown says so and links to Anthropic’s incident. A slowdown or maintenance shows as a small icon beside Claude’s usage bars, and every open problem is listed in Settings → General → Integrations.

It shows what Anthropic has posted, so in the first minutes of an outage the error in your terminal can arrive before the incident does. For that gap, the dropdown also notes when three of your turns fail on an overloaded or server error within five minutes: something seen on this Mac, not a report from Anthropic. Each check is an anonymous read with nothing about your sessions, made only for agents you use and never while your Mac sleeps. The same pass tells you when your Claude Code is out of date, with the command to update it. How Perch watches agent health.

Questions

Claude Code outages, answered

Is Claude Code down right now?
Check status.claude.com, Anthropic's official status page, and look at the Claude Code and Claude API rows. If both are operational and you still get errors, the cause is usually your login, your usage limit or your network, and the exact error says which.
Is status.anthropic.com the same as status.claude.com?
Yes. status.anthropic.com redirects to status.claude.com, which covers claude.ai, the Claude API, Claude Code and Anthropic's other products on one page.
Does a 529 Overloaded error count against my usage limit?
No. Claude Code's docs say a 529 means the API is at capacity across all users and doesn't count against your quota. Capacity is tracked per model, so switching with /model often works while the one you were using is busy.
Why does claude.ai work when Claude Code doesn't?
They're separate rows on the status page, so one can have an incident while the other is fine. And some causes are Claude Code's alone: an ANTHROPIC_API_KEY or ANTHROPIC_BASE_URL in your shell overrides the login claude.ai uses. Run /status in Claude Code to see which credential is active.
Does Claude Code retry on its own?
Yes. Server errors, overloads and timeouts that arrive before any of the answer has streamed are retried automatically, up to 10 times by default. By the time you see one of those errors, Claude Code has already tried again.
Can Perch tell me when Codex, Amp, Devin or Droid are down?
Yes. Perch reads the official status pages of Claude Code, Codex, Amp, Devin (Windsurf's page) and Droid, and shows the same red banner when the part an agent uses is down. Only agents you use on your Mac are checked.

The same guide for Codex, Amp, Devin and Droid.