What actually caused this?

Anthropic has not published a detailed cause in the information available. The status note says the issue has been resolved. For any further detail, check the official status page at https://stspg.io/n57njqf1mk5l.

Could this happen again?

Yes. Any tool can have another outage. Anthropic runs a large, complex service and has a strong track record, but no service is immune. That is exactly why watching it matters rather than assuming it is always fine.

How do I find out the next time Claude has a problem?

NoCrash reads Claude's public status page every minute. When Anthropic reports a problem, NoCrash translates it into plain English and sends you a heads-up, usually within a minute of Anthropic's own report. You find out from a calm message rather than from a customer complaint.

Claude / Anthropic outage postmortem, June 22 2026

What happened

Claude, the AI service run by Anthropic, had a bigger problem starting at 00:37 UTC on June 22, 2026. It lasted about one hour and recovered at 02:07 UTC. Anthropic has since marked it resolved.

Who this hits and how they usually find out

If you have an n8n workflow that calls Claude, or an app that sends prompts to it, you probably did not know anything was wrong until something downstream broke. A customer got a blank response. A report did not arrive. A form submission went nowhere. That is the usual shape: not an alarm, just a confused customer asking why nothing happened. By the time you piece it together, the disruption is already over and the damage is done.

Why this is especially rough without a technical team

There is no error on your screen when a third-party tool goes quiet. Your workflow does not send you a message saying it stopped. The work just does not move. If you are not an engineer, you have no logs to check, no place to look. The first real signal is a customer who noticed before you did, which is a bad position to be in even when the fix is simple.

Timeline

00:37 UTC, June 22, 2026 – Claude started having a bigger problem.
About one hour – the disruption ran.
02:07 UTC, June 22, 2026 – Claude recovered and Anthropic marked it resolved.

How a watcher catches this before your users do

NoCrash reads Claude’s official public status page once 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 looking. That is the difference between “my customer just emailed me something is broken” and “I got a heads-up at 00:38 and knew what was happening.”

It also watches the things you ship. If you have n8n workflows, NoCrash can watch those through an API token. If you have an app, you can give it a URL or drop in a small JS snippet. So if the problem is on your side rather than Claude’s, that surfaces too, in the same place.

To be clear about what it does not do: NoCrash reads Claude’s own public status page. It does not find outages before Anthropic reports them. It catches the report within a minute and tells you in plain English, which is usually well before a customer notices.

Official source

For the authoritative account of this outage, see Anthropic’s own status page: https://stspg.io/n57njqf1mk5l