What happened
On September 2, 2026, Claude / Anthropic reported a bigger problem starting at 21:18 UTC. It lasted about one minute and was resolved by 21:20 UTC. Anthropic has since marked it as resolved. The status note gives no further detail about what went wrong.
Who this kind of outage hits and how they usually find out
If you run automations, workflows, or a product that calls Claude, even a one-minute gap can break a run silently. The automation does not scream. It just stops, or returns nothing, or queues up without telling you. You find out when a customer writes in to say their summary never arrived, or their draft is blank, or the thing they paid for did not happen. That gap between “it broke” and “I heard about it” is almost always measured in hours, sometimes days.
Why this is especially rough without a technical background
There are no logs to read. There is no red error on your screen. The work just stops moving and everything looks fine from where you sit. The first signal is usually a frustrated message from someone who expected a result. By then you are already behind, already explaining, already wondering how long it had been broken before anyone said anything. That is the shape of a quiet outage for a solo operator or a small team.
Timeline
- 21:18 UTC, September 2, 2026 - Claude / Anthropic reports a bigger problem begins.
- 21:20 UTC, September 2, 2026 - Claude / Anthropic marks the issue resolved.
- Total duration - about 1 minute.
How a watcher catches this before your users do
NoCrash reads Claude / Anthropic’s public status page every minute. The moment that page flips from working to having trouble, NoCrash sends you a plain-language heads-up, in words you can act on, within a minute of Anthropic’s own report. You do not have to check a separate page or remember to look. It sits next to everything else you build on, so one place tells you when any of them go sideways.
NoCrash also watches the things you ship. If you run n8n workflows, it watches those. If you have an app, you can give it a URL or drop in a small JS snippet and it will watch that too. So if something goes quiet on your own side, that surfaces as well.
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 outages before the tool’s own status page does. But it means you hear about it in plain English, right away, instead of from a customer.
The authoritative account
For the official record of this outage, see Anthropic’s own status page: https://stspg.io/9dgzwz3ymz42