AI API outages on November 5, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 5, 2026 (UTC) our probes attributed 4 outage(s) to 2 provider(s): Gemini API (Google): 3; yi-01ai API: 1. Providers’ own status pages opened 3 entries (OpenAI, baseten, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), yi-01ai API, OpenAI API, baseten API, nebius API, baichuan API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on November 5, 2026?
Yes, measured. 3 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 07:45 UTC, at least 4 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 |
|---|---|---|---|---|---|---|
| 03:41–03:45 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥4 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 07:45–07:45 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | http 503; timeout |
| 08:01–08:05 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥4 min | 2 | provider outage | http 503 |
| 13:01–13:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥4 min | 3 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 17:45–17:45 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | http 503; timeout |
Current Gemini API (Google) status
Was the yi-01ai API down on November 5, 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 16:40 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 16:40–16:45 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 2 | provider outage | timeout |
Was the OpenAI API down on November 5, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. OpenAI’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor ChatGPT Work and Dots Errors · resolved — UTC
Was the baseten API down on November 5, 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 Kimi-K3 on Model APIs. **Dedicated Inference is not affected** · resolved — UTC
Was the nebius API down on November 5, 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 Token Factory: some models unavailable in eu-north1 · resolved Nov 5, 11:07 UTC
Was the baichuan API down on November 5, 2026?
Not attributably. 3 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 |
|---|---|---|---|---|---|---|
| 00:40–01:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥35 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 04:20–04:20 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
| 18:55–18:55 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | [Errno 101] Network is unreachable |
Was the doubao API down on November 5, 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 |
|---|---|---|---|---|---|---|
| 05:25–05:26 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
Was the ernie API down on November 5, 2026?
Not attributably. 1 multi-region failure(s) of ernie coincided with failures of other providers, so the cause sat above ernie and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 11:40–11:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥11 min | 7 | shared with 2 other provider(s) — not attributed | http 503 |
Was the iflytek API down on November 5, 2026?
Not attributably. 4 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:05–01:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥10 min | 4 | shared with 2 other provider(s) — not attributed | timeout |
| 02:10–02:35 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥25 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 03:45–03:45 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 18:55–18:55 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
68 single-region failure(s) were also recorded that day (yi-01ai 23, google 17, iflytek 8, baichuan 7, doubao 4, friendli 2, featherless 1, inference-net 1, openai 1, anthropic 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: Nov 4 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0