Late on August 14, 2026, just before midnight UTC, Claude reported a bigger problem. It lasted about 23 minutes, recovering at 00:21 UTC on August 15. Anthropic has since marked it resolved.
Who this kind of outage hits, and how they usually find out
If you use Claude inside an n8n workflow, a customer-facing app, or any automated process, a 23-minute gap is not nothing. Drafts don’t get written. Summaries don’t come back. Support replies sit empty. The tool doesn’t shout when it stops working. It just goes quiet. Most operators find out the same way: a customer writes in asking why something didn’t happen, and only then does the scramble to figure out what broke begin. By that point the gap has already done its damage.
Why this is especially rough without a technical background
There is no error on your screen. There is no log file to open. The work simply stops moving and you have no way to know if the problem is Claude, your workflow, your own app, or something else entirely. You start second-guessing everything. Did I break something? Is it just me? That uncertainty is its own cost, separate from the outage itself. The first real signal is usually an unhappy customer, and that is a bad way to learn that a core tool went down half an hour ago.
What the timeline looked like
- 23:58 UTC, August 14, 2026 - Claude reported a bigger problem.
- 00:21 UTC, August 15, 2026 - Claude marked the issue resolved.
- Total duration - about 23 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 go check anything yourself. That turns “my customer told me something broke” into “I got a heads-up within a minute of Claude’s own report.” It also watches the specific things you ship: your n8n workflows and your app 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, sitting next to everything else you build on. NoCrash does not find the outage before Claude’s own status page does. It reads that page and tells you fast, in plain English, in one place.
For the authoritative account of this outage, see Claude’s official status history at https://stspg.io/vpnnwf2vhdv4.