Space for ads
Checked every 5 minutes · How we measure this
As of 23:50 EDT on 21 Sep 2026, claude.ai responded to our check in 127 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 6 minutes ago
The line is response time measured from our probe to claude.ai, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Claude on its own status page. Verify on their status page.
0 problem reports
Claude degraded performance
DownBits detected degraded performance on Claude between 22 Sep 2026, 06:35 – 07:50 IST, lasting ongoing. Detected across 15 consecutive automated checks of claude.ai.
Detected by DownBits probe
Elevated errors for multiple models
We have seen success rates return to normal across affected models, and are monitoring closely to ensure no further issues.
Confirmed on the vendor status page
Issues with Google Play subscriptions
We are aware of an issue affecting users interacting with subscriptions via Google Play, such as when creating a new subscription on Android devices. Google has confirmed an issue with Google Play, and we are awaiting their further updates.
Confirmed on the vendor status page
Claude degraded performance
DownBits detected degraded performance on Claude between 15 Sep 2026, 15:25 – 16:50 IST, lasting ongoing. Detected across 17 consecutive automated checks of claude.ai.
Detected by DownBits probe
Intermittent error spikes for Claude Mythos 5.1 and Claude Fable 5.1
A fix has been deployed for Claude Mythos 5.1 and Claude Fable 5.1 and we are monitoring to ensure it has resolved the issue.
Confirmed on the vendor status page
Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.
Confirmed on the vendor status page
Elevated latency on the Claude API for some users
We are experiencing slower than normal response times on the Claude API for some customers whose traffic enters through the US Midwest. Users may experience elevated latency and some request timeouts.
Confirmed on the vendor status page
Claude degraded performance
DownBits detected degraded performance on Claude between 10 Sep 2026, 21:30 – 00:55 IST, lasting ongoing. Detected across 1193 consecutive automated checks of claude.ai.
Detected by DownBits probe
Degraded functionality for Claude Cowork on Windows
A Windows update released September 8 has left Claude Cowork on Windows unable to run local commands, because its workspace can no longer reach your computer's drive. For most users, chat and file reading and editing still work. There's no in-app workaround yet, and restarting or reinstalling won't help. Microsoft has developed a fix and is working to release it. We'll post an update when we have more to share.
Confirmed on the vendor status page
Claude is responding normally. Our last automated check of claude.ai completed 6 minutes ago and succeeded in 127 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, Claude has been available 100.00% over 24 hours, 99.90% over 7 days, 99.90% over 30 days. We recorded 9 incidents in the last 30 days.
Claude has averaged 134 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to claude.ai and does not include rendering time in your browser.
The most recent incident DownBits recorded for Claude began on 22 September 2026 at 06:35 IST and lasted 1 hr 15 min. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching claude.ai normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://claude.ai/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Claude. On Windows run ping claude.ai and nslookup claude.ai in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load claude.ai in a private or incognito window. If it works there, clear cookies and site data for claude.ai in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
