AI API outages on October 25, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 25, 2026 (UTC) no AI API outage could be attributed to a provider: nothing failed from two or more regions at once without other providers failing alongside. Providers’ own status pages opened 2 entries (Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Claude API (Anthropic), writer API, yi-01ai API · all AI APIs, last 72 hours
Was the Claude API (Anthropic) down on October 25, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for Claude Sonnet 5.5 and other models · resolved Oct 25, 07:53 UTC
- major Elevated errors for Claude Fable 5.1 · resolved Oct 25, 08:49 UTC
Current Claude API (Anthropic) status
Was the writer API down on October 25, 2026?
Not attributably. 1 multi-region failure(s) of writer coincided with failures of other providers, so the cause sat above writer and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:09–10:05 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥536 min | 292 | shared with 4 other provider(s) — not attributed | http 503; timeout |
Was the yi-01ai API down on October 25, 2026?
Not attributably. 1 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 11:47–11:57 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
28 single-region failure(s) were also recorded that day (yi-01ai 15, sambanova 5, iflytek 2, friendli 1, baichuan 1, sensenova 1, stepfun 1, google 1, doubao 1). A failure seen from one region cannot be separated from a problem on that network path, so none of them is called an outage.
How is an outage told apart from a network problem?
Each provider is probed every five minutes from 4 independent regions. A failure is attributed to the provider only when it is seen from two or more regions at once and no other provider fails in the same minutes; a failure shared with other providers has a cause above all of them and is not blamed on anyone. Durations are lower bounds: we see the first and last failed probe, not the real start and end. Status-page entries are the provider’s own words, shown next to the measurement, not instead of it.
Previous: Oct 24 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0