On the evening of August 28, 2026, Claude had a significant disruption. It started at 17:22 UTC and lasted about two hours, recovering at 20:21 UTC. Anthropic has since marked it resolved. The facts are thin on detail, so this account stays honest and short on specifics.
Who this kind of outage hits, and how they usually find out
If you build on Claude, you are probably using it to power something a customer touches: a support flow, a writing tool, a summarizer inside your product. When Claude goes quiet, that thing stops working. The problem is that nothing inside your product screams at you. No red banner, no email from Anthropic at the moment it breaks. The first signal is usually a customer writing in to say something is broken, or just going silent. By then the damage is done and you are already behind.
Why this is especially rough without a technical background
A developer can pull logs, check error rates, and at least see the shape of the problem. If you are a solo founder or an automation operator, you have none of that. You just notice that a workflow has not fired, or a customer mentions the AI part of your product gave a strange response or no response at all. There is no error on your screen. The work simply stops moving and you find out the hard way.
Timeline
- 17:22 UTC - Claude’s public status page showed a bigger problem.
- ~19:22 UTC - Roughly two hours into the disruption.
- 20:21 UTC - Claude recovered. Anthropic marked the issue resolved.
Total duration: about two hours.
How a watcher catches this before your users do
NoCrash reads Claude’s public status page every minute. The moment Anthropic flips that page from working to having trouble, NoCrash sends you a plain-language message telling you what broke and when. You do not have to check anything. You do not have to wait for a customer to tell you.
That matters because two hours is a long time for a customer-facing AI feature to be broken without you knowing. Getting a calm heads-up at 17:22 UTC, in plain English, sitting next to everything else you build on, is a different experience from finding out at 20:00 UTC because someone complained.
NoCrash also watches the things you ship. If you run n8n workflows, it watches those. If you have an app, it watches a URL you give it or a small JS snippet you add. So if the problem is on your side rather than Claude’s, that surfaces too. What it does not do is find the outage before Anthropic’s own status page reports it. It reads that page and tells you quickly, in words you can act on.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/6rfby2z7stc2