On the evening of August 16, 2026, Claude had a major outage starting at 21:59 UTC. It lasted about 35 minutes and was resolved by 22:35 UTC. Anthropic has since marked it as resolved.
Who this kind of outage hits
If you build on Claude, you probably found out the wrong way. Not from a status page. From a customer saying something felt broken, or from noticing yourself that a workflow had gone quiet. That gap, between when the tool stopped working and when you heard about it, is where the damage happens. A paying customer files a complaint, a batch of automations silently stalls, and you are the last to know.
Why it is especially rough without an engineering team
When you are running a small operation, there are no logs to check and no engineer to page. The work just stops moving. Nothing on your screen turns red. An automation that should have run at 22:05 UTC simply did not, and you will not know that until you go looking or someone complains. By then you are already behind, already explaining yourself, already doing damage control on something that was never your fault.
Timeline
- 21:59 UTC – Claude stopped working. Major outage begins.
- 22:35 UTC – Claude recovered. Outage lasted about 35 minutes.
Anthropic has confirmed the issue is resolved.
How a watcher catches this before your users do
NoCrash reads Claude’s public status page every minute. The moment Anthropic’s own page flips from working to having trouble, NoCrash sends you a plain-language message telling you what is wrong, in words you can act on, without you having to go check anything yourself.
That matters because 35 minutes is long enough for a customer to notice, send a message, and start wondering whether your product is reliable. If you had gotten a calm heads-up at 21:59 UTC, you could have posted a quick note to your users, paused anything time-sensitive, or simply known not to promise a fast turnaround while Claude was out.
NoCrash also watches the things you ship on top of Claude. Your n8n workflows, and your app through a URL you give it or a small JS snippet. So if something goes quiet on your own side, that surfaces too, in the same place, in the same plain language.
The limit is honest: NoCrash reads Anthropic’s public status page and tells you within a minute of their own report. It does not find the outage before Anthropic does. But it means you hear about it right away, in plain English, instead of from a frustrated customer.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/cc6kmwrqhzmh