AI API outages on November 4, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 4, 2026 (UTC) our probes attributed 11 outage(s) to 2 provider(s): Gemini API (Google): 10; doubao API: 1. Providers’ own status pages opened 1 entry (OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), doubao API, OpenAI API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on November 4, 2026?
Yes, measured. 10 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 00:42 UTC, at least 36 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 |
|---|---|---|---|---|---|---|
| 00:42–00:45 | 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 |
| 01:05–01:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 08:20–08:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 13:01–13:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 14:01–14:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 14:25–14:25 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 14:41–14:45 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | provider outage | timeout |
| 15:01–15:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | provider outage | timeout |
| 15:21–15:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 15:41–15:45 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 16:01–16:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 2 other provider(s) — not attributed | timeout |
| 16:21–16:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 16:41–16:45 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥4 min | 3 | provider outage | timeout |
| 17:01–17:05 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | provider outage | timeout |
| 17:21–17:25 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥4 min | 3 | provider outage | timeout |
| 17:41–17:45 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | provider outage | timeout |
| 18:01–18:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥4 min | 3 | provider outage | http 503; timeout |
| 18:21–18:25 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥4 min | 4 | provider outage | http 503; timeout |
| 18:45–18:45 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
Current Gemini API (Google) status
Was the doubao API down on November 4, 2026?
Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 23:55 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 23:55–23:56 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | <5 min | 3 | provider outage | timeout |
Was the OpenAI API down on November 4, 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 Elevated error rates across paid ChatGPT plans · resolved — UTC
44 single-region failure(s) were also recorded that day (yi-01ai 24, iflytek 4, baichuan 3, doubao 2, stepfun 2, friendli 1, google 1, ernie 1, reka 1, featherless 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 3 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0