On the evening of July 25, 2026, Claude / Anthropic reported a bigger problem starting at 18:41 UTC. It lasted about an hour and was resolved by 19:45 UTC. Anthropic has since marked it as resolved. That is the full picture the official source gives us.
Who this kind of outage hits, and how they usually find out
If you pipe Claude into anything, a workflow that drafts replies, a tool that summarizes documents, an app that leans on the API, you are exposed the moment Claude goes quiet. The hard part is that nothing inside your product tells you. Your workflow does not send you a message saying “I stopped.” Your app does not throw a visible error. A customer tries to use the thing you built, gets nothing or gets something broken, and eventually they write to you. That is usually how you find out. Not from a log, not from an alert. From a frustrated person.
Why this is especially rough if you are not an engineer
An engineer can pull logs, check error rates, trace where a request died. If you are running a business on top of Claude and you are not that person, none of those doors are open to you. The work just stops moving. A summary does not arrive. A reply does not get drafted. There is no red light on your screen. The first signal is silence, and silence looks exactly like normal until a customer breaks it. By then you are already behind, already apologizing, already explaining something you did not know was happening.
Timeline
- 18:41 UTC, July 25, 2026 - Claude / Anthropic reports a bigger problem beginning.
- About one hour - the disruption runs.
- 19:45 UTC, July 25, 2026 - Anthropic marks the issue resolved.
How a watcher catches this before your users do
Anthropic publishes a public status page. NoCrash reads that page every minute. The moment it flips from working to having trouble, NoCrash sends you a plain-language message, in words you can act on, sitting next to everything else you build on. You find out within a minute of Anthropic’s own report, not within a minute of a customer complaint.
That matters because the gap between “Anthropic posted about this” and “my customer told me” can be an hour or more. NoCrash closes that gap. It does not find the outage before Anthropic does, and it does not guess at whether your app is healthy on its own. It reads what Anthropic says and tells you immediately, in plain English.
NoCrash also watches the things you ship: your n8n workflows through an API token, and your app through a URL or a small JS snippet. So if something goes quiet on your own side, that surfaces too, in the same place.
For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/zkm687kx885m