Claude had a significant disruption on July 9, 2026. It started at 03:28 UTC and lasted about 22 minutes, recovering at 03:51 UTC. Anthropic has since marked it resolved.
Who this kind of outage hits, and how they usually find out
If you run workflows, automations, or an app that calls Claude, a 22-minute window where it stops responding can quietly break a lot. The tool does not send you an email. There is no pop-up. Your automation just stalls, your users get nothing back, and you find out when someone writes in to ask why things are broken. That gap between “it stopped” and “you knew” is where the damage happens.
Why it is especially rough if you are not an engineer
You cannot open a log file and see what went wrong. There is no red error on your screen. The work just stops moving, and the silence looks exactly like everything being fine. The first real signal is often a frustrated customer, or a missed task you only notice hours later when you go looking. By then you are already behind, already explaining yourself, already wondering how long it had been broken before anyone said anything.
Timeline
- 03:28 UTC, July 9, 2026 - Claude starts showing a bigger problem.
- 03:51 UTC, July 9, 2026 - Claude recovers. The disruption lasted about 22 minutes.
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, in one place, next to everything else you build on. You do not have to be watching. You do not have to be awake at 03:28 UTC.
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 own side, that surfaces as well.
The honest version: NoCrash catches the trouble within a minute of Anthropic’s own report. It does not find the outage before Anthropic does. What it does is make sure you hear about it in plain English, fast, without having to check anything yourself.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/sddyj2h6b61s