Claude Goes Dark: Anthropic's Chatbot Hits the Skids Across Its Newest Models

Key points

• Anthropic's Claude assistant started throwing errors at around 9:41 AM ET on 3 September 2026.
• The outage hits seven models: Mythos 5.1, Fable 5.1, Mythos 5, Fable 5, Opus 5, Opus 4.8 and Opus 4.6.
• Anthropic said at 10:49 AM ET it had identified the cause but was still working on a fix.
• Users are seeing failed requests and error responses when they try to chat with the affected models.
• No security incident has been claimed or confirmed. This looks, so far, like a plain reliability failure.

Claude is having a bad morning.

Anthropic, the company behind the Claude chatbot, confirmed on its official status page that users are hitting errors when they try to send requests to several of its flagship models. The trouble started at roughly 9:41 AM Eastern Time on 3 September 2026 and, at the time of writing, is still going.

This is the third Anthropic outage we have covered since July, following a server-overload failure on 29 July and a broader authentication and service collapse on 16 August. The pattern is worth noting: three incidents in six weeks, each affecting different parts of the stack.

For anyone who doesn't use Claude directly, this is a useful reminder that a large slice of the software people now depend on runs through a handful of AI providers, and when one of them sneezes, a lot of dashboards go red.

Which models are broken?

Seven Claude models are affected, spanning Anthropic's newest releases and older ones still running in production.

Anthropic first flagged elevated errors on three models, then expanded the list a few minutes later. The full set, per the company's own updates, is below.

Requests to these models are either failing outright or returning errors instead of a normal response. Applications built on top of Claude, think customer support bots, coding assistants, internal search tools, will inherit that same failure.

What actually caused it?

We don't know yet. Anthropic has said it identified the underlying issue but hasn't shared what it is.

By 10:49 AM ET the company confirmed engineers were still working on a fix. That's the entire public detail. No mention of a security incident, no attack, no bad deploy. Until Anthropic publishes a post-incident writeup, anything more specific is guessing.

This was first reported by BleepingComputer as a straight availability story, and that's still the honest framing. A model going down is not, by itself, a security event. It becomes one only if the cause turns out to be malicious, or if the fallback behaviour of apps built on Claude does something unsafe, say, silently switching to a less-restricted model with different safety filters.

Should users and businesses be worried?

Ordinary users should wait. Retrying may or may not help while Anthropic is still working the issue.

For businesses that have wired Claude into a product, this outage is a practical test: does your app fail loudly, or does it hang and retry forever without telling anyone? A few things worth checking while Claude is down:

1. Are your Claude API calls timing out cleanly, or piling up?
2. If you have a fallback model configured, is it one you actually trust for the same task?
3. Are error messages reaching the humans who need to see them, not just the logs?

We'll update this piece when Anthropic publishes a cause. Not a breach, not a poisoning, not a jailbreak. Just a very visible reminder that AI infrastructure is still infrastructure, and infrastructure breaks.