On the evening of August 20, 2026, Claude by Anthropic reported a bigger problem starting at 19:16 UTC. It lasted about 26 minutes and was marked resolved at 19:43 UTC. Anthropic has confirmed the issue is resolved, but has not published a detailed cause.
Who this kind of outage hits
If you run automations or an app that calls Claude, you probably did not have a status page open at 19:16. You were doing something else. The first sign something was wrong was likely a workflow that quietly stopped producing output, or a customer who tried a feature and got nothing back. That is the usual shape of this: not an alarm, just silence, and then an email or a message from someone who paid you.
Why silence is the hardest kind of problem
There is no error on your screen when a third-party tool goes quiet. Your automation does not send you a note. The work just stops moving, and you have no logs to read because the problem is not on your side. By the time a customer tells you something is broken, the disruption may already be over, but the damage to trust is done. A 26-minute window is short enough that many operators would only find out after the fact, if at all.
Timeline
- 19:16 UTC - Claude / Anthropic reports a bigger problem.
- 19:43 UTC - Claude / Anthropic marks the issue resolved.
- Total duration - about 26 minutes.
How a watcher catches this before your users do
NoCrash reads Claude’s public status page 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 you having to check anything yourself. That turns “my customer told me an hour later” into “I got a calm heads-up within a minute of Anthropic’s own report.”
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 in the same place. One view, plain English, no hunting across tabs.
To be clear about what it does not do: NoCrash reads what the tool’s own status page says. It does not find the outage before the tool reports it. It just makes sure you hear about it right away, in plain language, instead of from a frustrated user.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/w7yghz6hfr72