AI API outages on November 1, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 1, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): Gemini API (Google): 1; yi-01ai API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), yi-01ai API, baichuan API, doubao API, iflytek API, targon API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on November 1, 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 10:02 UTC, at least 3 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:02–10:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | provider outage | timeout |
| 17:02–17:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 17:22–17:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 22:02–22:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
Current Gemini API (Google) status
Was the yi-01ai API down on November 1, 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 10:40 UTC, at least 20 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:40–11:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥20 min | 4 | provider outage | timeout |
Was the baichuan API down on November 1, 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 |
|---|---|---|---|---|---|---|
| 05:30–05:35 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 4 | shared with 2 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Was the doubao API down on November 1, 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 |
|---|---|---|---|---|---|---|
| 23:05–23:05 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Was the iflytek API down on November 1, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 05:30–05:40 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥10 min | 5 | shared with 2 other provider(s) — not attributed | timeout |
Was the targon API down on November 1, 2026?
Not attributably. 1 multi-region failure(s) of targon coincided with failures of other providers, so the cause sat above targon and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:52–16:10 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥18 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
55 single-region failure(s) were also recorded that day (yi-01ai 31, iflytek 6, doubao 4, deepseek 3, targon 2, sambanova 2, friendli 1, google 1, openai 1, siliconflow 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 31 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0