How to check whether Claude is down right now
Open Anthropic’s official Claude status page and check the affected service and incident timestamp. A problem with sign-in, the API or Claude Code may affect only that service. This article does not provide a live status feed.
- Check whether an active incident matches your error and service.
- If no matching incident is listed, try a fresh session or another browser and check your connection.
- For API or coding errors, record the error message and time before retrying. Avoid repeatedly submitting a paid task while its earlier attempt is unresolved.
Historical scope: the timeline below covers examples through October 7, 2026. Those incidents do not establish whether Claude is down today. Jump to the detailed status-checking steps.
Reviewed by Imran Khan Pathan, Editor at AI Tech Safar. I use Claude Code daily for parts of this blog’s workflow, so I’ve personally hit several of the incidents catalogued below – including the September 3 one, mid-task. This piece cross-references Anthropic’s own status page history against independent outage trackers (Downdetector, StatusGator, IsDown) and press reports rather than relying on a single source’s incident count. Where trackers disagree, the text says so.
Last updated: October 7, 2026

What changed since the September version
- New incidents: September 11, 15, 22 and 29, plus October 1, 5 and 6, and an August 28 upstream-provider failure that the earlier version missed.
- Corrections: Claude’s September 3 incident lasted 3h 06m by Anthropic’s count, not about five hours, and its cause differed from ChatGPT’s and Grok’s. The “28 outages in 30 days” figure came from IncidentHub, not from TechTimes’ own counting.
- Also added: the June 12 to July 1 export-control suspension, which wasn’t a technical outage but kept two models offline for 18 days.
How to Check If Claude Is Down Right Now
This article is a static explainer, not a live tracker. Here’s where to get the real-time answer:
- Anthropic’s official status page (status.claude.com) – the authoritative source. It tracks six components: claude.ai, the Console (platform.claude.com), the API, Claude Code, Cowork and Claude for Government.
- Downdetector or StatusGator – real-time user-report spikes, useful for confirming it isn’t just your connection.
- r/ClaudeAI on Reddit – the community usually confirms outages within minutes.
- Check whether it’s model-specific. Several 2026 incidents hit only certain models while everything else stayed up, so “Claude is down” isn’t always the full picture. Try switching models before assuming a total outage.
The status page has its own failure modes. On August 14, status.claude.com served an invalid certificate and was unreachable for almost three hours, at the exact moment people needed it. A degradation on Fable 5 that began at 20:00 UTC the same day wasn’t acknowledged until 23:57 UTC, and on September 11 the first status post appeared a minute before that incident ended. If the page won’t load or looks too calm, trust Downdetector and X as a cross-check.
🟢 Live status embed below – this loads Anthropic’s actual status page directly, so it always reflects the current state, not what it looked like when this article was published.
What Happened on September 29, 2026 (Historical Incident)
This was the widest outage of the year so far, because it hit every surface at once and, unlike most incidents, knocked out sign-in itself.
- 14:21 UTC: Anthropic’s status page opened an incident for elevated errors on claude.ai (including the desktop and mobile apps), Claude Code and Cowork.
- 14:28 UTC: the notice widened to include the Claude API.
- 14:30 UTC: platform.claude.com was added. The page showed claude.ai, Claude Code and Cowork in partial outage, and the Console and API in degraded performance.
- About 14:59 UTC: Anthropic said most services had recovered. Signing in, new chats, voice conversations, Claude Code and Cowork sessions, purchases and file uploads were working again, though some sign-in attempts and sessions were still failing.
- 8:30 AM PT (15:30 UTC): Anthropic reported everything back to normal. Its status log counts the incident at roughly two hours, which is why trackers quote slightly different durations.
TechRadar reported more than 11,800 Downdetector reports within about 20 minutes. We couldn’t find a published explanation of the root cause. It came a week after a September 22 incident that hit several Claude models, and the status page logged no incidents at all between those two dates.
What Happened on September 3, 2026 (When ChatGPT and Grok Went Down Too)
This outage got attention for a reason beyond Claude: ChatGPT and Grok had problems in the same window. The details matter, because the three incidents didn’t share one cause.
- Claude: Anthropic’s status page began logging elevated errors at about 9:26 AM ET, first on Mythos 5.1, Fable 5.1 and Opus 5, later widening to Mythos 5, Fable 5, Opus 4.8, Opus 4.6 and Sonnet 5. The incident lasted 3 hours 6 minutes, and Anthropic’s spokesperson called it an infrastructure issue that caused a partial outage across claude.ai, Claude Code, Cowork and the API.
- ChatGPT: OpenAI said a routing error starting around 7:43 AM PT made ChatGPT and Codex unavailable for some users. Its incident was resolved at 12:55 PM ET.
- Grok: SpaceXAI blamed an outage at its Memphis compute center, and its status page logged 3 hours 37 minutes.
Some outlets pointed to a shared Microsoft Azure East US problem, based on StatusGator reports, but none of the three companies confirmed it, and Cloudflare said it had no significant disruption. Model-hopping likely made things worse: when ChatGPT, which drew the most reports, went down, users piled onto Claude and Grok. So treat it as a coincidence with possible shared pressure, not as one proven root cause. We also found no official Google incident for Gemini that day.
One correction to the earlier version of this article: it listed the Claude incident at about five hours. Anthropic’s own status record is 3h 06m, though trackers built on user reports logged longer tails.
What Happened on August 24? (Two Outages, Same Day)
The August 24 outage began with Anthropic’s first status notice at 05:06 UTC, and it ran for roughly three hours, closing at 08:30 UTC. That put 529 Overloaded errors right at the start of the US work week.
Services affected: claude.ai, the Claude API, Claude Code and Claude Cowork. The Console and Claude for Government stayed up.
Models hit: Claude Opus 5, Fable 5, Mythos 5 and Opus 4.8.
The sequence on the status page: at 05:06 UTC Anthropic said it was investigating; by 05:27 UTC it said the cause had been identified and a fix was underway; at 06:42 UTC the incident was still unresolved; and it was marked resolved at 08:30 UTC. The cause was never publicly disclosed, and no postmortem followed. “529 Overloaded” is what many users saw, but Anthropic never said overload was the root cause.
Then it happened again the same day. Around 16:00 UTC users hit login errors on claude.ai and Claude Code subscription connections, a separate and much shorter incident of about six minutes.
The stat that stands out most: IncidentHub’s tracking, reported by TechTimes on August 24, counted 28 outages in the 30 days leading up to that date for commercial Claude. Claude for Government logged 100% uptime over 90 days on the status page – same company, separate infrastructure tier, a different reliability record.
What Happened on August 13? (The Previous 3-Hour Outage)
Eleven days earlier, Claude went down starting around 14:34 UTC and recovered about three hours later. Affected models were Mythos 5, Fable 5 and Sonnet 5. Anthropic logged it as “elevated errors on multiple models” with no root cause.
What Has Happened Since: October 1-7, 2026
The newest models have been the weak spot this month, and the incidents have been brief:
- October 1: a delayed-credits problem on the Claude Platform, flagged as minor, plus about two hours of degraded API and Console performance.
- October 5: elevated errors on Mythos 5.1 and Fable 5.1 from 12:40 to 13:10 UTC (5:40 to 6:10 AM PT).
- October 6: elevated errors on Opus 5.5 from 12:24 to about 12:43 UTC.
- October 7: elevated errors loading usage data on platform.claude.com for about an hour, per StatusGator.
Mythos 5.1 and Fable 5.1, which launched on September 1, have now appeared in incident notices repeatedly: September 3, 11, 15 and 22, and October 5. One tracker calls the October 5 failure their fifth in five weeks. Newly launched models draw heavy demand, which fits capacity strain, but Anthropic hasn’t said that’s the cause.
Why Does Claude Keep Going Down? Root Causes by Category
Anthropic has been candid in some postmortems and quiet in others. Here’s what’s actually been disclosed across 2026, grouped by cause:
- Capacity constraints. The June 2 outage, 5 hours 44 minutes from 06:04 to 11:49 UTC, was attributed to “unexpected capacity constraints,” with free-plan users seeing a message that Claude couldn’t respond because demand outpaced compute. One outlet claimed a Claude Code sub-agent bug set off the collapse, but Anthropic’s status updates never confirmed it.
- Network failures. The July 29-30 incident involved multiple network failures that cut serving capacity, producing widespread 529 Overloaded errors while Anthropic rerouted traffic. Full recovery took until late on the 30th.
- Authentication failures. The August 16 incident (21:58-22:34 UTC, 36 minutes) began with users unable to authenticate and spread into degraded performance across claude.ai, the Console, the API, Claude Code and Cowork.
- Upstream providers. On August 28, Cowork and Claude Code on the web failed for roughly three hours, and Anthropic blamed an upstream cloud provider, the first time in this run it pointed outside its own stack.
- Infrastructure bugs. An earlier postmortem disclosed overlapping bugs that degraded response quality for a small share of requests. Anthropic was explicit that it doesn’t intentionally reduce model quality because of demand or server load; those were routing bugs, not throttling.
Anthropic’s postmortems, when published, tend to be detailed and non-defensive. The recurring problem is that one doesn’t always follow. Several incidents, including the August 24 and September 29 ones above, closed with no public explanation of what actually broke.
Not every outage is technical. Between June 12 and July 1, Claude Fable 5 and Mythos 5 were unavailable worldwide for 18 days after a US export-control order, a regulatory event rather than a failure. If a model disappears for everyone at once with no error codes, that’s a different category of problem.
Which Claude Services Go Down During an Outage?
Not everything breaks at once. The general pattern across 2026:
- Almost always affected: claude.ai, the Claude API, Claude Code, Claude Cowork and, sometimes, authentication and login paths specifically.
- Sometimes affected: the Console, individual model versions only (leaving others usable), and the Claude Agent SDK.
- Usually unaffected: Claude for Government, which runs on separate infrastructure and has a much better uptime record than the commercial product.
Important nuance: the API and the consumer web interface don’t always fail together, but they can. During the March 11 incident, the web and Claude Code were affected while the API was not. On August 16 and September 29, though, authentication and the API both failed alongside claude.ai, so “I’ll just use the API” isn’t a guaranteed workaround.
Full 2026 Claude Outage Timeline
| Date | Duration | Root Cause (as disclosed) |
|---|---|---|
| Jan 22, 2026 | Hours | Elevated error rates |
| Mar 2, 2026 | Several hours | “Unprecedented demand”; login failures |
| Mar 11, 2026 | Hours | Elevated errors on claude.ai and Claude Code; API not affected |
| Apr 15, 2026 | ~3 hrs | Elevated errors, login issues |
| May 14, 2026 | Unspecified | 2,000+ Downdetector reports |
| May 22, 2026 | Unspecified | Elevated error rate across models |
| Jun 2, 2026 | 5h 44m | “Unexpected capacity constraints” – longest of 2026 |
| Jun 5, 2026 | ~2 hrs | All models; recovered model by model (Opus 4.6 first, Opus 4.8 last) |
| Jun 12 – Jul 1, 2026 | 18 days | Not a technical outage: US export-control order forced a worldwide suspension of Fable 5 and Mythos 5 |
| Jun 23, 2026 | ~1 hr+ | API errors; 8,000+ Downdetector reports |
| Jul 17, 2026 | 1h 32m | Server overload, 529 errors |
| Jul 29-30, 2026 | 24+ hrs (intermittent) | Multiple network failures |
| Aug 13, 2026 | ~3 hrs | Not disclosed |
| Aug 14, 2026 | ~3 hrs (status page); 24 min (services) | status.claude.com served an invalid certificate; separate API, Code and Cowork incident |
| Aug 16, 2026 | 36 min | Authentication failure that spread to five products |
| Aug 20, 2026 | 26 min | Not disclosed |
| Aug 24, 2026 (AM) | ~3 hrs | Not disclosed; 529 Overloaded errors |
| Aug 24, 2026 (PM) | 6 min | Login errors |
| Aug 28, 2026 | ~3 hrs | Cowork and Claude Code on the web; Anthropic blamed an upstream cloud provider |
| Sep 3, 2026 | 3h 06m | “Infrastructure issue” per Anthropic; coincided with ChatGPT and Grok outages with separate causes |
| Sep 11, 2026 | ~20 min | Elevated errors on Mythos 5.1 and Fable 5.1 |
| Sep 15, 2026 | ~1.5 hrs | Intermittent error spikes on Mythos 5.1 and Fable 5.1 |
| Sep 22, 2026 | ~1-1.5 hrs | Elevated errors on multiple models; not disclosed |
| Sep 29, 2026 | ~2 hrs | Sign-in and service failures across claude.ai, API, Code and Cowork; not disclosed |
| Oct 1, 2026 | 6h 15m (minor) | Delayed credits on the Claude Platform; API degraded for about 2 hrs |
| Oct 5, 2026 | 30 min | Elevated errors on Mythos 5.1 and Fable 5.1 (12:40-13:10 UTC) |
| Oct 6, 2026 | 19 min | Elevated errors on Opus 5.5 |
The Bigger Pattern: Two Rough Months
The September 29 incident capped a stretch that started in mid-August. One tracker counted 18 incidents between August 12 and August 31, and the status page logged 13 more in September, so counts of “how many outages” vary by how each tracker splits and merges them. Another tracker, Pulsetic, logged 86 incidents of all sizes between July 8 and October 6, including minor ones.
What made this stretch different from a normal bad week:
- It opened with eight consecutive days with no clean day in mid-August, hitting model endpoints, platform surfaces and authentication in turn.
- It shifted into login, connector and billing failures that switching to a backup model wouldn’t fix, since the problem wasn’t the model itself.
- It then settled into repeated brief failures on the newest models, while headline uptime improved.
That last point is worth holding onto. Monthly uptime moved from 99.01% in July to 99.70% in September, so the picture is mixed: fewer long outages, but a steady drip of short ones. The practical lesson for anyone building on Claude hasn’t changed. A single-vendor dependency means Anthropic’s downtime becomes your downtime, so if Claude Code or the API is load-bearing for your workflow, a documented fallback is a better plan than hoping outages stay rare.
Common Claude Error Messages, Explained
| Error | What It Usually Means |
|---|---|
| HTTP 500 (Internal Server Error) | A problem on Anthropic’s servers, not your account or connection – check the status page. |
| HTTP 529 (Overloaded) | Claude’s servers are receiving more requests than they can currently handle – typically clears on its own, so retry after a short wait. |
| “Request couldn’t be processed” | The generic failure message people saw on September 29, when sign-in and chat both failed together. |
| Claude Code authentication errors | A recurring failure category in 2026 – it hits sign-in and is separate from model-response issues. |
| “Elevated errors for multiple models” | Anthropic’s standard status-page wording for a partial, model-specific incident – not necessarily a full outage. |
What to Do While Claude Is Down
- Check whether it’s model-specific first. Several 2026 incidents left one model broken while the rest worked. If Opus 5.5 is erroring, try Sonnet 5.5 or another model before assuming a full outage.
- Check which component is affected. If only Claude Code is failing, claude.ai may work fine, and the reverse. The status page lists them separately.
- For 529 errors, retry with a delay. If you call the API, build in exponential backoff instead of hammering the endpoint, which only adds load.
- If Claude is load-bearing for you, keep a fallback ready. That means a second model or provider you’ve already tested, not one you’ll try for the first time mid-incident.
- Use the time to cross-check. If the status page is quiet but Downdetector is spiking, believe the spike and look for a model-specific incident on the page.
FAQ
Should I log out and back in when Claude shows sign-in errors?
No. During the September 29 login failure, Anthropic told people who were already signed in not to sign out, because the sign-in system itself was failing and a fresh login could leave you locked out until it recovered. If you’ve already been logged out, wait for the status page to show the issue resolved before trying again.
Will I lose my messages or work if Claude goes down mid-task?
Possibly. During the September 29 outage, some users reported unsaved messages being lost. The safe habit is to copy long prompts and important replies into a notes app before you send or rely on them. Anthropic hasn’t published a guarantee about in-progress work during an incident, so treat anything not yet saved as at risk.
What’s the difference between degraded performance, partial outage and major outage?
These are the status page’s severity labels. Degraded performance generally means slower responses or an occasional failure, partial outage means a real share of requests or users are failing, and major outage means the component is largely unusable. On September 29, claude.ai, Claude Code and Cowork showed partial outage while the API and Console showed degraded performance.
Is there a time of day when Claude is more likely to fail?
Our tally of the seven major incidents since September 3 found five that started between roughly 12:20 and 14:30 UTC. That’s 8:20 to 10:30 AM on the US East Coast and about 5:50 to 8:00 PM in India. It’s a small sample and Anthropic hasn’t said why, so treat it as a pattern to watch, not a rule.
How long should I wait before switching to a fallback?
Since September 3, six of the seven major incidents ended within about two hours, and the exception ran just over three. A sensible rule is to wait 20 to 30 minutes if the work isn’t urgent, then move to another model or tool. If a task is time-critical, don’t wait at all and keep a backup ready in advance.
What if I was charged or bought credits during an outage and didn’t get what I paid for?
Check the status page’s billing notices first. On October 1, Anthropic had a delayed-credits issue on the Claude Platform: credits purchased didn’t apply right away, and the company said it was resolved by 22:36 UTC. A separate Google Play subscription issue on September 16 lasted 32 minutes. If a charge still hasn’t been matched with access, contact Anthropic support with your receipt.
Related Reading on AI Tech Safar
- How to Use ChatGPT Work (Formerly Agent Mode)
- Mastering the GPT-6 Astra Ecosystem
- OpenAI’s Rogue AI Agents: The $500,000-a-Day Review
- Meta Muse AI Agent: Features, Pricing, Safety & Complete Guide
Useful Sources
- Claude Status – Official Incident History
- The Register – ChatGPT, Claude and Grok all go down at once
- Chasms – ChatGPT, Claude and Grok Outage: What Happened on September 3
- Computing – Azure failure likely brought down ChatGPT, Claude and Grok
- Digital Trends – Anthropic’s Claude is having a major breakdown today (September 29)
- The Next Web – Claude is down as Anthropic investigates errors across its services
- Unite.AI – Anthropic reports service disruption across claude.ai, Code, Cowork and API
- Unite.AI – Anthropic outage disrupts Claude services after login failures (August 16)
- BleepingComputer – Anthropic confirms Claude is down in major outage
- TechTimes – Commercial Claude has gone down 28 times in 30 days
- The Next Web – Claude outage hits multiple models again (August 24)
- Tech Insider – Claude outage hits 7h 9m as Anthropic tops $47B (June 2)
- DeployFlow – Claude outage tracker and failover guidance
- StatusGator – Claude status history
For the broader context and related reading, explore our AI Models 2026: Comparing Gemini, GPT, Claude and More.

