Anthropic favicon

Anthropic outage on 2026-10-24

claude.com
October 2026 24 Major incident

Anthropic logged two separate error spikes on Claude models in the early hours of 24 October, the longer one lasting 39 minutes. Both were fixed on Anthropic's side, not yours, affecting claude.ai and api.anthropic.com.

Started

00:31 UTC

Duration

Lasted 12m

Source

IsDown

Next time

Anthropic is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: claude.ai, api.anthropic.com

What happened?

Anthropic's status page shows two incidents inside a few hours. The first began at 00:31 UTC, when Anthropic reported elevated errors on requests to Claude Opus 5.5. That one was resolved six minutes later, with Anthropic stating the actual impact window ran from 00:23 to 00:34 UTC, 12 minutes in total. The second started at 05:16 UTC, affecting Claude Fable 5 and Claude Fable 5.1, described the same way: elevated errors on requests. Anthropic identified a cause internally at 05:24, deployed a fix by 05:41, and declared it resolved at 05:53, with the stated impact window running from 05:00 to 05:35 UTC, 39 minutes long. Neither update names what broke beyond "elevated errors," and Anthropic has not published any further detail or post-mortem for either incident. No user reports were filed during either window on this record. Both components on Anthropic's list, claude.ai and api.anthropic.com, are flagged as affected across the two incidents. Over the past 90 days Anthropic has logged 52 incidents with a median duration of 56 minutes, so both of today's incidents resolved faster than that median. Across all time Anthropic's status page has recorded 845 incidents.

Learning

When a provider reports "elevated errors" without naming the failing layer, you are left to decide for yourself whether your own integration was affected, and a one-line status update carries real limits as evidence: it tells you something went wrong somewhere between request and response, not which part of the stack. Over the last 30 days UptimeRobot's own checks against Anthropic recorded 13 incidents, all resolved, with a median duration of 40 minutes, a figure built independently of Anthropic's own count and timing. The two numbers do not have to match to both be true: Anthropic's own count of 52 incidents over 90 days reflects what it chooses to file, while an external probe hitting the API directly sees every failure regardless of whether Anthropic writes it up. A spike like this usually sits in request handling or model routing rather than anything visible from a client's side, which is why watching your own endpoints alone would not have caught it. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.