AI API outages on October 26, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 26, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): Gemini API (Google): 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), OpenAI API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 26, 2026?
Yes, measured. 1 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 18:05 UTC, at least 13 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:05–12:17 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥13 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 12:37–13:02 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥25 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 13:19–13:22 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥4 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 13:39–17:45 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥246 min | 49 | shared with 1 other provider(s) — not attributed | timeout |
| 18:05–18:17 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥13 min | 2 | provider outage | timeout |
Current Gemini API (Google) status
Was the OpenAI API down on October 26, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. 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 for Ads POST requests · resolved Oct 26, 18:30 UTC
41 single-region failure(s) were also recorded that day (yi-01ai 29, iflytek 3, deepinfra 2, sambanova 2, fireworks 1, hunyuan 1, cerebras 1, sensenova 1, doubao 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 25 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0