Is Claude AI Down — How to Check in 60 Seconds

Wondering is Claude AI down right now, or is the problem on your end? The fastest way to find out is Anthropic’s official status page at status.anthropic.com — it lists every Claude component (claude.ai, the API, the Console, Claude Code) and shows any active incident within minutes of Anthropic confirming one. This guide is the playbook I follow every time Claude misbehaves: where to check first, what each error message actually means, how to tell an Anthropic outage from a problem with your account or network, and what to do while you wait.

TL;DR: Check status.anthropic.com first — it covers claude.ai, the Claude API, the Console, Claude Code, Claude Cowork, and Claude for Government separately. A 529 “overloaded” error or a capacity message means Anthropic’s side; a 401/403 or a problem on only your device means your side. DownDetector and social media surface outages a few minutes before the official page updates. If you’re on the API, exponential-backoff retries and a fallback model handle most incidents without code changes. Most Claude outages are partial and resolve within an hour or two.

How to Check If Claude AI Is Down: The 60-Second Playbook

When Claude stops responding, run through these five checks in order. In my experience the answer arrives at step one or two the vast majority of the time.

1. Open status.anthropic.com. This is Anthropic’s official status page (it currently redirects to status.claude.com — same page). Each component has its own status line, so check the one you’re actually using: claude.ai for the chat app, Claude API for integrations, Claude Code for the coding tool. An orange or red banner with “Investigating” or “Identified” means the problem is confirmed on their end. You’re done — skip to the “what to do while it’s down” section.
2. Look for a banner inside claude.ai. During larger incidents Anthropic often shows a notice at the top of the chat interface itself, sometimes before the status page updates.
3. Check DownDetector. Search “Claude” on downdetector.com. A sudden spike of user reports is a strong signal even when the official page still shows green — crowd reports typically lead the official acknowledgment by 5–15 minutes.
4. Scan social media. Search “Claude down” on X or check r/ClaudeAI on Reddit. If hundreds of people are posting the same error in the last ten minutes, it’s not you.
5. Run a cross-check. Try a different model in the model picker, a different browser or device, or (if you’re a developer) a minimal API call. If one path works and another doesn’t, you’ve narrowed the failure to a specific component — which matters, because Claude incidents are frequently partial.

One thing worth internalizing: “Claude is down” is rarely one single thing. Anthropic’s status page tracks claude.ai, the Claude Console, the Claude API, Claude Code, Claude Cowork, and Claude for Government as separate components, and incidents regularly affect one without touching the others. For a full walkthrough of that page — components, severity levels, and how to subscribe to alerts — see our guide to reading the Claude AI status page.

Is It You or Anthropic? A Quick Diagnosis

Before you assume an outage, walk through this decision path. It mirrors how I triage Claude problems myself, and it usually takes under two minutes.

claude.ai won’t load at all

If the page never renders or you get a browser-level error, test another site first. If everything else loads fine, try claude.ai in a private/incognito window. A page that loads in incognito but not in your normal window points to a stale cache, a cookie problem, or an interfering extension — clear site data for claude.ai and retry. If the page fails everywhere, check the status page: a full front-end outage will show claude.ai as degraded or in “Major Outage.”

You can log in, but messages fail or hang

This is the classic mid-incident symptom: the app shell loads (it’s mostly static), but the model backend is struggling. If you’re seeing capacity or “unable to respond” messages, that’s Anthropic-side congestion, not your account. Try switching models — during partial incidents one model family often keeps working while another is degraded. If every model fails and DownDetector is spiking, it’s an outage.

Login itself fails

Login failures split two ways. If the login screen errors for everyone (check social media), the authentication service is having an incident. If it’s just you — wrong verification code, a magic-link email that never arrives, an SSO loop — the fix is usually on your side: check spam for the login email, confirm you’re using the same sign-in method you registered with (Google vs. email), and disable aggressive privacy extensions that block third-party auth requests. Repeated “too many attempts” messages mean you’ve been temporarily rate-limited on login; wait 15–30 minutes.

Claude works, but it’s unusually slow

Slow responses sit in a gray zone. Long prompts with big attachments and extended thinking are legitimately slower — that’s expected behavior, not degradation. But if a prompt that normally streams within a couple of seconds sits silent for 30+ seconds, or streaming repeatedly stalls mid-response, Anthropic may be running in a degraded state that never gets a formal incident. The status page’s “Degraded Performance” state exists for exactly this. If nothing is posted, it can still be worth waiting out the peak-hour crush (US weekday afternoons are consistently the busiest window in my testing).

You hit a message or usage limit

A message saying you’ve reached your limit and when it resets is not an outage — it’s your plan’s usage cap working as designed. Free-plan caps reset on a rolling basis, and Pro uses 5-hour session windows plus a weekly cap. If you’re hitting these often, our breakdown of Claude AI limits on free vs. Pro explains exactly how the caps work and how to stretch them.

Claude Error Messages Decoded

Claude’s error messages are more informative than they look. Here’s the field guide, covering both the chat app and the API.

Error / message	What it means	Whose problem
“Due to unexpected capacity constraints, Claude is unable to respond”	Anthropic’s serving capacity is saturated — demand spike or degraded infrastructure	Anthropic — retry in a few minutes
529 overloaded_error (API)	The API is temporarily overloaded; your request was shed to protect the service	Anthropic — back off and retry
500 api_error (API)	An unexpected internal error on Anthropic’s side	Anthropic — retry; check status page if persistent
429 rate_limit_error (API)	You exceeded your tier’s requests-per-minute or tokens-per-minute limit — not an outage	You — respect the retry-after header
401 / 403 (API)	Authentication or permission failure — bad key, revoked key, or insufficient access	You — check your key in the Console
“Something went wrong” / message fails to send (claude.ai)	Generic frontend-to-backend failure; common during partial incidents	Either — retry once, then check the status page
Response stalls mid-stream	Streaming connection dropped or backend degraded	Either — regenerate; persistent stalls suggest degradation
Usage limit reached (with reset time)	Your plan’s cap, working as designed	You — wait for reset or upgrade

The single most useful distinction in that table is 429 vs. 529. Both are “slow down” signals, but a 429 means you exceeded your quota, while a 529 means Anthropic’s service is overloaded for everyone. A spike of 529s across your logs is a mini-outage signal; a spike of 429s means you need to look at your own request patterns — our guide to Claude API rate limits covers the tier system and how to stay under the caps.

What to Do While Claude AI Is Down

If you use claude.ai (Free, Pro, or Max)

• Don’t hammer refresh. Retrying every few seconds adds load and won’t get you in faster. Check the status page, then retry every 5–10 minutes.
• Switch models. Partial incidents often hit one model while others stay up. If your default model errors, try another from the picker.
• Try another surface. The desktop apps, mobile apps, and web app share a backend but occasionally fail differently during frontend-specific incidents.
• Your data is safe. Outages affect availability, not stored conversations. Your chat history will be there when service returns.
• Keep a fallback for genuine emergencies. If you’re on a deadline, having a second assistant bookmarked beats waiting. Our roundup of Claude AI alternatives covers the realistic stopgaps.

If you use the Claude API

Outages are where good client design pays off. Three patterns handle almost every incident:

1. Retry with exponential backoff and jitter. Treat 529 and 500 as retryable; treat 429 as retryable after the retry-after delay. The official Python and TypeScript SDKs already retry transient errors automatically — make sure you haven’t disabled that behavior.
2. Fail over across models. If your primary model returns repeated 529s, fall back to a sibling (for example, Sonnet when Opus is degraded). Incidents scoped to a single model family are common — a model-level fallback keeps you serving traffic.
3. Queue what can wait. Anything not user-facing (batch classification, embeddings-style pipelines, report generation) belongs in a queue you can drain after recovery — or in the Message Batches API, which tolerates delay by design.

A simple backoff loop looks like this:

import time, random, anthropic

client = anthropic.Anthropic()

def call_with_backoff(max_retries=5, **kwargs):
    for attempt in range(max_retries):
        try:
            return client.messages.create(**kwargs)
        except anthropic.APIStatusError as e:
            if e.status_code in (429, 500, 529) and attempt < max_retries - 1:
                delay = min(2 ** attempt + random.random(), 60)
                time.sleep(delay)
            else:
                raise

During a confirmed incident, also consider pausing non-critical cron jobs. Piling queued retries onto a recovering service is how you turn Anthropic’s outage into your own.

Where Claude Outage Reports Show Up First

Different sources have different lag. Knowing the order helps you calibrate how much to trust each one:

• Your own errors (0 minutes). You are your own earliest detector. A sudden burst of 529s or failed sends is signal, even before anyone else confirms it.
• X and Reddit (2–10 minutes). Searching “Claude down” sorted by latest gives you an instant crowd read. r/ClaudeAI threads fill up fast during real outages. The noise floor is high, though — a handful of complaints at any given moment is normal.
• DownDetector (5–15 minutes). Aggregated user reports with a spike chart. Good for confirming scale; the comment section also surfaces which specific error people are seeing.
• status.anthropic.com (typically 5–20 minutes). The authoritative source, but it requires a human at Anthropic to confirm and post the incident, so it lags crowd reports slightly. Once posted, it’s the best place to follow progress: incidents move through Investigating → Identified → Monitoring → Resolved with timestamped updates.

If you’d rather be notified than go looking, the status page supports email, SMS, Slack, webhook, and RSS subscriptions — and for context on how often incidents actually happen and what tends to cause them, see our Claude AI incident history and outage log.

One pattern I’ve noticed after tracking several incidents: the crowd signal and the official signal are complements, not competitors. DownDetector tells you that something is wrong and roughly how widespread it is; the status page tells you what is wrong, which components are affected, and when Anthropic expects to fix it. During the June 2026 elevated-error incident, for example, user reports appeared within minutes, and Anthropic’s status page moved from “Investigating” to “Identified” in about six minutes — fast, but the crowd was still first. Use both.

Common Mistakes When Claude Stops Responding

• Confusing usage limits with outages. “You’ve reached your limit” is a cap, not downtime. No amount of waiting out an “outage” will fix it before your reset time.
• Treating a 429 like a 529. Retrying a 429 aggressively makes it worse — you’re already over quota. Respect the retry-after header.
• Checking only claude.ai status when you’re an API user. The components fail independently. The chat app being up tells you little about api.anthropic.com, and vice versa.
• Assuming green means perfect. The status page reflects confirmed incidents. Brief or regional degradation can exist before anything is posted — your own error rates and crowd reports fill that gap.
• Rage-clicking regenerate. During capacity incidents, every retry joins the same overloaded queue. Spacing retries out genuinely improves your odds.
• Blaming the model for infrastructure problems. Slow or failed responses during an incident say nothing about Claude’s quality. Judge the model when the platform is healthy.

The Bottom Line

When you’re asking “is Claude AI down,” the answer is one bookmark away: status.anthropic.com tells you what Anthropic has confirmed, DownDetector and social media tell you what the crowd is seeing right now, and your own error messages tell you whether the problem is their infrastructure or your account. Most incidents are partial and short-lived — a model switch or a ten-minute wait solves the majority of them. For everything else in this cluster, start at our Claude status hub.

FAQ