Is Claude down right now?
Checking…Verifying live status…
Our latest checks found Claude responding normally. Live verification is running now.
Your report feeds the live outage-velocity detector. One click per 30 s.
Live latency (probe round-trip, ms)
User reports, last 24 hours
Outage history
last 30 days
Recent outages and issues we recorded for Claude, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.
No problemsProblemsOutageNot monitored
What Claude reported
last 30 days
Taken from Claude's own published incident feed. These are their words about their own service, shown here so you can compare them with what we measured. Scheduled maintenance and test posts are filtered out.
Comments
Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.
Comments are loading in our built-in box because Disqus was blocked or unavailable. Spam and abuse are filtered automatically, and comments are hidden once 3 readers flag them.
How we check Claude
No evidence of problems with Claude. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.
Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Claude's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Claude normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.
Claude (claude.ai) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.
Common Claude problems users report
- Chat interface loads but requests hang without responding
- Login page appears but authentication fails or times out
- API calls return 5xx errors or connection refused
- Responses arrive extremely slowly or incomplete
What to do when Claude is not working
First check the banner above. If it shows evidence of problems, the fault is most likely on Claude's side and waiting is usually the only option. If it shows nothing wrong, try accessing Claude from a different network (mobile data instead of WiFi), clear your browser cache and cookies, or test the API with a simple curl request to confirm whether the web interface or backend is the issue.
About Claude
Claude is an AI assistant that helps users with writing, analysis, math, coding, and creative tasks through a web interface and API. When Claude is down or degraded, users cannot access the chat interface, submit new requests, or receive responses to their queries. API users experience failed requests and cannot integrate Claude's capabilities into their applications.
Official Claude resources
Cross-check an incident with the company's own channels:
- Official Claude status pageTheir own incident dashboard
- Claude help centerSupport articles and contact options
Frequently asked questions
Is Claude down right now?
No. Our checks are finding no problems with Claude right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Claude continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.
What usually goes wrong with Claude?
The problems visitors report most often on this page are can't connect, no response / timing out, API errors, can't log in, slow or laggy and 5xx error pages. Those are the options the report button offers for Claude, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.
Why is Claude not responding for me when this page says it is fine?
Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Claude specifically, Claude's chat service, API inference backend, and authentication systems can fail independently, and regional routing may direct some users to degraded infrastructure while others connect normally. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.
How do I tell whether it is Claude or my own connection?
For Claude, try submitting a simple question like 'what is 2+2' in a fresh browser tab in incognito mode, and wait 30 seconds for a response. A problem that follows you across networks and devices is very unlikely to be yours.
What should I do while Claude is down?
If this page shows evidence of problems, the fault is most likely on Claude's side. Specifically: avoid submitting the same prompt repeatedly, as queued requests may eventually process and create duplicate work once service recovers. Reporting it here helps other people see they are not alone.
How does status.buzz check Claude?
Continuously, around the clock. Claude publishes a machine-readable status feed, so our first check reads it directly and reports what Claude itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.
Does Claude have an official status page?
Yes, at status.claude.com, and it is linked further up this page. That is Claude's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.
Is status.buzz affiliated with Claude?
No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Claude or claude.ai. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Claude's own support, not us.
No comments yet. Be the first to describe what you're seeing.