AI API outages on November 20, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 20, 2026 (UTC) our probes attributed 4 outage(s) to 2 provider(s): Gemini API (Google): 2; sensenova API: 2.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), sensenova API, baichuan API, doubao API, iflytek API, siliconflow API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on November 20, 2026?
Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 14:01 UTC, at least 2 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:01–14:02 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), US (Central) | <5 min | 2 | provider outage | timeout |
| 15:01–15:02 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | <5 min | 3 | provider outage | timeout |
Current Gemini API (Google) status
Was the sensenova API down on November 20, 2026?
Yes, measured. 2 outage(s) attributed to sensenova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 22:41 UTC, at least 1 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:06–00:07 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 06:01–06:03 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥1 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 09:56–09:57 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
| 22:41–22:42 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
| 23:41–23:42 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | <5 min | 3 | provider outage | timeout |
Was the baichuan API down on November 20, 2026?
Not attributably. 2 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 |
|---|---|---|---|---|---|---|
| 04:01–04:03 | host probes | 2 of 4: South America (Santiago), US (Central) | ≥1 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
| 05:18–05:32 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago) | ≥15 min | 3 | shared with 5 other provider(s) — not attributed | timeout |
Was the doubao API down on November 20, 2026?
Not attributably. 2 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 |
|---|---|---|---|---|---|---|
| 06:01–06:27 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥25 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 08:06–08:07 | 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 20, 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 |
|---|---|---|---|---|---|---|
| 03:53–04:08 | host probes | 2 of 4: Asia (Tokyo), South America (Santiago) | ≥15 min | 3 | shared with 4 other provider(s) — not attributed | timeout |
| 04:42–04:43 | host probes | 2 of 4: South America (Santiago), US (Central) | ≥1 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 06:12–06:23 | host probes | 2 of 4: Asia (Tokyo), South America (Santiago) | ≥11 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 08:33–08:42 | host probes | 2 of 4: Asia (Tokyo), South America (Santiago) | ≥9 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Was the siliconflow API down on November 20, 2026?
Not attributably. 1 multi-region failure(s) of siliconflow coincided with failures of other providers, so the cause sat above siliconflow and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 09:53–10:43 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥50 min | 41 | shared with 3 other provider(s) — not attributed | http 503 |
Current siliconflow API status
48 single-region failure(s) were also recorded that day (sambanova 15, baichuan 7, iflytek 7, doubao 6, google 5, sensenova 2, aleph-alpha 1, hyperbolic 1, openai 1, stepfun 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 19 · Last 72 hours · Next: Nov 21
Machine-readable: incidents.json · Licence: CC BY 4.0