Is Claude Down?

No — Claude is up

Reachable from all 8 checked regions

Average response time: 433ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.claude.com

Claude uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

201ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 22 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak

Jul 25 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

155ms

DNS 0ms TCP 1ms TLS 27ms TTFB 141ms

bom

365ms

DNS 0ms TCP 3ms TLS 11ms TTFB 351ms

cdg

124ms

DNS 0ms TCP 1ms TLS 12ms TTFB 110ms

dfw

155ms

DNS 0ms TCP 1ms TLS 12ms TTFB 144ms

ewr

92ms

DNS 0ms TCP 2ms TLS 9ms TTFB 81ms

fra

190ms

DNS 0ms TCP 1ms TLS 11ms TTFB 174ms

gru

130ms

DNS 0ms TCP 3ms TLS 12ms TTFB 95ms

iad

1994ms

DNS 0ms TCP 1ms TLS 9ms TTFB 1984ms

jnb

421ms

DNS 0ms TCP 0ms TLS 8ms TTFB 412ms

What Claude does

Claude is Anthropic's AI assistant, used through the claude.ai web app, desktop and mobile apps, Claude Code in the terminal, and an API that other products build on. Because so many tools call Claude models rather than running their own, an Anthropic incident often surfaces inside unrelated software that never mentions Claude by name.

What an outage looks like

Outages are frequently per-model rather than total. Anthropic has posted degraded performance on a single model while the others served traffic normally, and recovery often arrives model by model across one incident. Raised error rates and latency are the usual shape rather than a hard outage, so applications built on the API tend to surface it as their own intermittent errors.

What to do about it

Check status.claude.com, which reports claude.ai, the Claude Console at platform.claude.com, the API at api.anthropic.com, Claude Code, Claude Cowork and Claude for Government separately, each with its own 90-day uptime figure. Incidents usually name the affected model, so switching models is a genuine workaround here in a way it is not for most services. status.anthropic.com redirects to the same page.

Is it down for everyone, or just you?

If this page says Claude is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Claude outage FAQ

Is Claude down, or just the model I am using?

Check which model the incident names. Anthropic's status page regularly posts degraded performance on one specific model, such as a single Sonnet or Opus version, while the others keep serving requests. Switching models in the app or in an API call is often enough to keep working. That distinction is unusual, and it is why the overall banner can look healthy during a real problem.

Does an Anthropic outage affect apps that are not Claude?

Yes, and that is the most common way people meet one. The Claude API at api.anthropic.com is tracked as its own component, and many products call it for their AI features without naming the provider anywhere in their interface. If an unrelated tool's assistant starts erroring while the rest of that tool works normally, checking status.claude.com is a reasonable next step.

Is Claude Code affected when claude.ai is down?

Not necessarily. Anthropic tracks Claude Code as a separate component from claude.ai, the Console and the API, each carrying its own 90-day uptime figure, so they can and do diverge. If the terminal tool fails while the web app answers normally, read the Claude Code line specifically rather than trusting the top-level status banner.

Why does status.anthropic.com show a different address?

It redirects to status.claude.com, which is now the canonical status page. Both reach the same dashboard covering claude.ai, the Console, the API, Claude Code, Claude Cowork and Claude for Government. Anthropic has been consolidating onto claude.com, and console.anthropic.com forwards there too, so older anthropic.com links generally redirect rather than break.

How we measure this

We request Claude's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Claude publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Claude goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required