AI API outages on October 28, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 28, 2026 (UTC) our probes attributed 4 outage(s) to 3 provider(s): yi-01ai API: 2; Gemini API (Google): 1; glm API: 1. Providers’ own status pages opened 3 entries (Anthropic, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: yi-01ai API, Gemini API (Google), glm API, Claude API (Anthropic), nebius API, baichuan API · all AI APIs, last 72 hours
Was the yi-01ai API down on October 28, 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 10:55 UTC, at least 43 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:55–11:10 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 2 | provider outage | timeout |
| 12:22–12:50 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥28 min | 5 | provider outage | timeout |
Was the Gemini API (Google) down on October 28, 2026?
Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 4 of 4 regions at once while no other provider was failing, first at 16:40 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:02–14:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥83 min | 15 | shared with 4 other provider(s) — not attributed | http 503; timeout |
| 14:42–16:02 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥80 min | 16 | shared with 2 other provider(s) — not attributed | timeout |
| 16:20–16:22 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥2 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 16:40–16:45 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥5 min | 4 | provider outage | timeout |
| 17:02–18:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥83 min | 17 | shared with 2 other provider(s) — not attributed | timeout |
Current Gemini API (Google) status
Was the glm API down on October 28, 2026?
Yes, measured. 1 outage(s) attributed to glm: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 20:55 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 20:55–20:55 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | [Errno 101] Network is unreachable |
Was the Claude API (Anthropic) down on October 28, 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:
- minor Elevated errors affecting the Gmail connector · resolved Oct 28, 05:48 UTC
- minor Elevated errors affecting the Google Calendar connector · resolved Oct 28, 20:05 UTC
Current Claude API (Anthropic) status
Was the nebius API down on October 28, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- major Compute Cloud: disk images and snapshots partial unavailability · resolved Oct 28, 17:54 UTC
Was the baichuan API down on October 28, 2026?
Not attributably. 1 multi-region failure(s) of baichuan coincided with failures of other providers, so the cause sat above baichuan and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:35–14:35 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
37 single-region failure(s) were also recorded that day (yi-01ai 20, sambanova 4, stepfun 3, sensenova 2, iflytek 2, baichuan 2, doubao 2, google 1, targon 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 27 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0