AI API outages on October 23, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 23, 2026 (UTC) our probes attributed 3 outage(s) to 2 provider(s): yi-01ai API: 2; Gemini API (Google): 1. Providers’ own status pages opened 5 entries (OpenAI, Anthropic, baseten).
This page is history. Is it down right now?
Live status, updated every 30 minutes: yi-01ai API, Gemini API (Google), OpenAI API, Claude API (Anthropic), baseten API, doubao API · all AI APIs, last 72 hours
Was the yi-01ai API down on October 23, 2026?
Yes, measured. 2 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 07:47 UTC, at least 7 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 07:47–07:50 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥3 min | 2 | provider outage | timeout |
| 14:44–14:47 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥4 min | 2 | provider outage | timeout |
Was the Gemini API (Google) down on October 23, 2026?
Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 13:19 UTC, at least 9 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:19–13:27 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥9 min | 2 | provider outage | timeout |
| 13:55–14:27 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥32 min | 7 | shared with 2 other provider(s) — not attributed | timeout |
| 15:35–15:47 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥12 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 16:59–17:35 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥37 min | 7 | shared with 2 other provider(s) — not attributed | timeout |
Current Gemini API (Google) status
Was the OpenAI API down on October 23, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- notice Delays in customer support responses · resolved Oct 23, 05:58 UTC
- notice Help Center Chat Support Degraded · resolved Oct 23, 22:02 UTC
- minor Degraded experience with ChatGPT app connections using CIMD · resolved Oct 23, 23:43 UTC
Was the Claude API (Anthropic) down on October 23, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- critical Elevated errors for Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5 · resolved Oct 24, 00:11 UTC
Current Claude API (Anthropic) status
Was the baseten API down on October 23, 2026?
Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on baseten’s status page, not verified by our probes:
- minor Elevated errors for US-only GLM 5.3 Flash on Model APIs · resolved Oct 23, 02:48 UTC
Was the doubao API down on October 23, 2026?
Not attributably. 1 multi-region failure(s) of doubao coincided with failures of other providers, so the cause sat above doubao and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 09:30–09:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥14 min | 9 | shared with 1 other provider(s) — not attributed | timeout |
41 single-region failure(s) were also recorded that day (yi-01ai 21, google 6, featherless 5, writer 2, iflytek 2, minimax 1, sambanova 1, baichuan 1, stepfun 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 22 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0