On the evening of July 25, 2026, Claude / Anthropic reported a bigger problem starting at 21:35 UTC. It lasted about 33 minutes and was resolved by 22:09 UTC. Anthropic has since confirmed the issue is resolved.
Who this kind of outage hits, and how they usually find out
If you build on Claude, your automations, your AI-assisted features, or your workflows quietly stopped getting responses during that window. Most people find out the wrong way: a customer writes in to say something is broken, or a colleague notices a report never arrived, or a queue of jobs just sat there untouched. Nothing inside the tool sends you a message. You are left piecing together a timeline after the fact, often hours later, while the customer is already frustrated.
Why this is especially rough if you are not an engineer
There is no error on your screen. There is no log to read. The work just stops moving. If you are a solo operator or a small team without a dedicated technical person, you have no obvious place to look. You might assume the problem is on your side, spend time checking your own setup, and only later realize the tool itself was the issue. By then, the customer has already formed an opinion.
Timeline
- 21:35 UTC – Claude / Anthropic reported a bigger problem.
- 22:09 UTC – Claude / Anthropic confirmed the issue was resolved.
- Total duration – about 33 minutes.
How a watcher catches this before your users do
NoCrash reads Claude / Anthropic’s public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message, in plain English, sitting next to everything else you build on. You hear about it within a minute of Anthropic’s own public report, not from a customer complaint an hour later.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, it watches that through a URL you give it or a small JS snippet you drop in. So if something goes quiet on your own side, that surfaces too, separately from what the tool’s status page says.
To be clear about what this is: NoCrash reads public status pages and watches the specific things you point it at. It does not find outages before the tool’s own status page does. It does not make independent judgments about whether a third-party service is healthy. What it does is make sure you are not the last to know when a tool you depend on reports trouble.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/9w9f5y5k2vwx