Live status check

Is Claude down right now?

We check claude.ai from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of claude.ai runs in your browser. If no result appears, run the check on the start page.

Our last check

Not checked yet — a fresh check starts when you open this page.

About Claude problems

Claude problems can show up as error messages in the chat, answers that do not finish, or trouble signing in, while claude.ai itself may still load. Usage limits on your plan can stop new messages for a while without any outage. Anthropic's Claude status page lists claude.ai and the API, so check it first when errors appear for everyone.

Official information

Claude official status page (verified )

Our check and Claude's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

Claude help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical Claude problems

An editorial list of typical problems, not based on live user reports.

General fixes: AI

  1. Read the exact message AI services can show usage limits and real errors as different messages. A limit message may say when you can continue, while a general error can point to a problem on the service's side.
  2. Start a new conversation Very long conversations or large attachments can fail on their own. Ask the same question in a new chat, with a smaller file if you attached one.
  3. Keep a copy of long prompts Write long prompts in a text editor first. If an answer breaks off or the page reloads, you can paste the prompt again instead of retyping it.
  4. Check the API key and usage For API access, compare the key, the project and the remaining quota in the provider's console before you change your code.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.