AI API outages on October 24, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 24, 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 3 entries (Anthropic, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Claude API (Anthropic), Gemini API (Google), nebius API, yi-01ai API · all AI APIs, last 72 hours
Was the Claude API (Anthropic) down on October 24, 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 Opus 5.5 · resolved Oct 24, 00:37 UTC
- major Elevated errors for Claude Fable 5 and Claude Fable 5.1 · resolved Oct 24, 05:53 UTC
Current Claude API (Anthropic) status
Was the Gemini API (Google) down on October 24, 2026?
Not attributably. 2 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:55–15:19 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥24 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 15:57–16:17 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥20 min | 3 | shared with 1 other provider(s) — not attributed | http 503; timeout |
Current Gemini API (Google) status
Was the nebius API down on October 24, 2026?
Not attributably. 2 multi-region failure(s) of nebius coincided with failures of other providers, so the cause sat above nebius and is not blamed on it. nebius’s own status page opened 1 entry that day (self-reported, listed below).
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:12–12:30 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥17 min | 5 | shared with 2 other provider(s) — not attributed | http 503 |
| 12:50–13:43 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥54 min | 16 | shared with 1 other provider(s) — not attributed | http 503 |
Self-reported on nebius’s status page, not verified by our probes:
- major Token Factory 503 errors in eu-west2 · resolved Oct 24, 14:24 UTC
Was the yi-01ai API down on October 24, 2026?
Not attributably. 3 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 |
|---|---|---|---|---|---|---|
| 02:22–02:37 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 13:37–13:42 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 15:17–15:27 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
49 single-region failure(s) were also recorded that day (yi-01ai 27, google 4, stepfun 4, doubao 3, iflytek 3, sensenova 2, openai 1, baichuan 1, featherless 1, writer 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 23 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0