AI API outages on November 3, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 3, 2026 (UTC) our probes attributed 12 outage(s) to 4 provider(s): Gemini API (Google): 8; Cerebras API: 2; aleph-alpha API: 1; baichuan API: 1. Providers’ own status pages opened 2 entries (Cerebras, OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), Cerebras API, aleph-alpha API, baichuan API, OpenAI API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on November 3, 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 14:42 UTC, at least 11 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 |
|---|---|---|---|---|---|---|
| 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 | shared with 1 other provider(s) — not attributed | timeout |
| 14:02–14: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 | timeout |
| 14:22–14: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 |
| 14:42–14: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 |
| 15:02–15: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 |
| 15:22–15:25 | 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 |
| 15:42–15:45 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥3 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 16:02–16: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:05–17:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | 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 |
| 17:45–17:45 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
| 18:05–18:05 | 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 |
| 19:05–19:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
Current Gemini API (Google) status
Was the Cerebras API down on November 3, 2026?
Yes, measured. 2 outage(s) attributed to Cerebras: host probes, requests to gpt-oss-120b failed from up to 4 of 4 regions at once while no other provider was failing, first at 16:55 UTC, at least 2 minutes observed in total. At least once Cerebras’s own host answered with an HTTP 5xx. Cerebras’s own status page opened 1 entry that day (self-reported, listed below).
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 16:55–16:57 | requests to gpt-oss-120b | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥2 min | 4 | provider outage | http 502; timeout |
| 16:55–16:55 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
Self-reported on Cerebras’s status page, not verified by our probes:
- notice Partial Service Disruption · resolved Nov 3, 19:41 UTC
Was the aleph-alpha API down on November 3, 2026?
Yes, measured. 1 outage(s) attributed to aleph-alpha: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 08:50 UTC, at least 15 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 08:50–09:05 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥15 min | 6 | provider outage | timeout |
Current aleph-alpha API status
Was the baichuan API down on November 3, 2026?
Yes, measured. 1 outage(s) attributed to baichuan: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 05:45 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:45–05:50 | 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 3, 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 File upload errors in ChatGPT · resolved Nov 3, 05:39 UTC
61 single-region failure(s) were also recorded that day (yi-01ai 29, friendli 5, doubao 5, sambanova 4, google 3, inference-net 3, baichuan 2, iflytek 2, cerebras 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 2 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0