Claude: problems reported

The problem is reported by Claude itself. The site still answers our check, so it may affect only some features or regions.

Official status
Partially Degraded Service

From status.claude.com, read 4 min ago.

Our check, from Germany
Answered in 109 ms

Request to claude.ai, 4 min ago. 286 of 288 checks in the last 24 hours succeeded, median 87 ms.

Is Claude working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Affected parts, according to Claude

Claude Console (platform.claude.com)
Degraded performance

Open incidents

monitoringMajor impactStarted Oct 7, 13:25 UTC

We've mitigated the errors loading usage data on platform.claude.com and in the Admin API usage report. While we work on a full fix, the most recent ~30 minutes of usage may take longer to appear on the platform.claude.com. API requests are not affected, and we will provide additional updates here.

Response time, last 24 hours

measured from our server in Germany
0 ms5 s10 s12:0016:0020:0000:0004:0008:00
Time to first responseFailed check
One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

  1. Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
  2. Try a private window. Open the site in a private (incognito) window. If it loads there, a browser extension or stale cookies are in the way: clear the site's cookies and cached files, then disable extensions one at a time.
  3. Try another browser. If the site works in a different browser, update or reset the one that fails.
  4. Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
  5. Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
    ipconfig /flushdns
  6. Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
  7. Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.
Guides that mention Claude

Recent incidents

from the official feed, read 7 min ago
ResolvedStarted Oct 7, 21:23 UTCResolved Oct 7, 21:23 UTC

We have identified an issue which resulted in some organizations to be incorrectly paused for having reached their spend limit, resulting in refused requests on the Claude API, Claude.ai, Claude Code, Claude Security, and Claude Cowork. This is now resolved.

ResolvedStarted Oct 7, 01:20 UTCResolved Oct 7, 02:33 UTC

This incident has been resolved. From 17:00 PT on October 6 / 00:00 UTC on October 7 to 18:40 PT on October 6 / 01:40 UTC on October 7, many requests to load usage data on the platform.claude.com Usage page and the Admin API usage report returned errors.

ResolvedStarted Oct 6, 12:24 UTCResolved Oct 6, 12:43 UTC

The issue affecting Claude Opus 5.5 has been resolved.

ResolvedStarted Oct 5, 13:05 UTCResolved Oct 5, 13:21 UTC

The issue affecting Claude Mythos 5.1 and Claude Fable 5.1 has been resolved. Impact occurred from 05:40 PT / 12:40 UTC to 06:10 PT / 13:10 UTC.

ResolvedStarted Oct 1, 16:20 UTCResolved Oct 1, 22:36 UTC

This issue has been resolved.

ResolvedStarted Sep 29, 14:21 UTCResolved Sep 29, 16:27 UTC

The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.

ResolvedStarted Sep 22, 00:57 UTCResolved Sep 22, 02:35 UTC

This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.

ResolvedStarted Sep 16, 16:18 UTCResolved Sep 16, 16:51 UTC

This issue has been resolved.

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,322 members already hereThey read, write, comment and vote. 0 verified · 31 joined this year

Cookies

We use essential cookies to run the platform. Analytics and marketing cookies are only turned on once you consent — you can change your choice at any time.