On July 21, 2026, Claude stopped working for about 28 minutes. The disruption started at 11:20 UTC and was resolved by 11:48 UTC. Anthropic has since marked it resolved. No detailed cause has been published.
Who this kind of outage hits
If you run automations or a product built on Claude, you probably did not have an alert waiting for you. Most operators find out the same way: a customer writes in to say something is broken, or they notice a queue of work that never moved. By then the outage may already be over, but the damage, a missed response, a stalled workflow, a confused user, is already done. The tool itself rarely sends you a message. You are just expected to be watching.
Why it is especially rough without a technical background
When Claude goes quiet, there is no error on your screen. Your n8n workflow does not throw a red flag you can read. The run just stops, or it retries silently, or it sits there. If you are not an engineer, you have no logs to dig through and no obvious place to look. The first real signal is often a customer asking why something did not happen. That is a bad way to find out, and it puts you on the back foot immediately, explaining a problem you only just learned about yourself.
What the timeline looked like
- 11:20 UTC – Claude stopped working. Major outage begins.
- 11:20 to 11:48 UTC – About 28 minutes of disruption.
- 11:48 UTC – Claude recovered. Anthropic marked the issue resolved.
Twenty-eight minutes is short in absolute terms. But if a customer tried to use your product during that window, it was long enough to matter.
How a watcher catches this before your users do
NoCrash reads Claude’s official public status page once every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, without needing to interpret anything technical. You find out within a minute of Anthropic’s own public report, not an hour later when a customer complains.
It also watches the things you ship. If you have n8n workflows, NoCrash watches those through your API token. If you have an app, you can give it a URL or drop in a small JS snippet, and it watches that too. So if something goes quiet on your side, that surfaces as well, sitting next to everything else in one place.
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 the outage before Anthropic’s own status page does. It just makes sure you are not the last to know.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/cqjf2860m4yy