AI API outages on October 16, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 16, 2026 (UTC) our probes attributed 10 outage(s) to 3 provider(s): Gemini API (Google): 8; doubao API: 1; yi-01ai API: 1. Providers’ own status pages opened 1 entry (nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), doubao API, yi-01ai API, nebius API, glm API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 16, 2026?
Yes, measured. 8 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 07:30 UTC, at least 40 minutes observed in total. At least once Google’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 07:30–07:30 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | http 503 |
| 09:02–09:22 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥20 min | 3 | shared with 1 other provider(s) — not attributed | http 503 |
| 09:43–09:50 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥7 min | 2 | provider outage | http 503; timeout |
| 12:10–12:10 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 12:50–12:50 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 13:10–13:43 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥33 min | 5 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 14:30–14:30 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 14:50–14:50 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503 |
| 15:10–15:30 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 6 | provider outage | http 503; timeout |
| 16:10–16:30 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 5 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 16:50–16:50 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | http 503; timeout |
| 17:10–17:10 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | http 503; timeout |
| 17:50–17:50 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | http 503; timeout |
| 18:10–18:10 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 18:30–18:43 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥13 min | 3 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 19:10–19:10 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | http 503 |
| 20:10–20:22 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥13 min | 2 | provider outage | http 503; timeout |
Is the Gemini API (Google) down right now? Live status →
Was the doubao API down on October 16, 2026?
Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 03:00 UTC, at least 18 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 02:05–02:08 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥3 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 03:00–03:18 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥18 min | 6 | provider outage | timeout |
Is the doubao API down right now? Live status →
Was the yi-01ai API down on October 16, 2026?
Yes, measured. 1 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 01:05 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:05–01:10 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 2 | provider outage | timeout |
Is the yi-01ai API down right now? Live status →
Was the nebius API down on October 16, 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 CLI login issues · resolved Oct 16, 13:13 UTC
Is the nebius API down right now? Live status →
Was the glm API down on October 16, 2026?
Not attributably. 1 multi-region failure(s) of glm coincided with failures of other providers, so the cause sat above glm and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:43–12:52 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥10 min | 5 | shared with 1 other provider(s) — not attributed | http 502; http 504 |
Is the glm API down right now? Live status →
44 single-region failure(s) were also recorded that day (yi-01ai 17, google 10, iflytek 4, stepfun 2, sensenova 2, baichuan 2, together 1, doubao 1, writer 1, mistral 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.
Machine-readable: incidents.json · Licence: CC BY 4.0