AI API outages on October 29, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 29, 2026 (UTC) our probes attributed 10 outage(s) to 2 provider(s): Gemini API (Google): 9; targon API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), targon API, SambaNova API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 29, 2026?
Yes, measured. 9 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 13:22 UTC, at least 24 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 |
|---|---|---|---|---|---|---|
| 13:02–13:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥3 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 13:22–13:25 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 3 | provider outage | timeout |
| 13:42–13:45 | 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 2 other provider(s) — not attributed | timeout |
| 14:02–14:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥3 min | 3 | shared with 1 other provider(s) — not attributed | http 503; 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 | shared with 1 other provider(s) — not attributed | 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 | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | provider outage | http 503; 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 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 16:22–16: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 |
| 16:42–16: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 |
| 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 | provider outage | timeout |
| 17:22–17:25 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥3 min | 2 | provider outage | timeout |
| 17:42–17:45 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥3 min | 3 | provider outage | timeout |
| 18:02–18: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 |
Current Gemini API (Google) status
Was the targon API down on October 29, 2026?
Yes, measured. 1 outage(s) attributed to targon: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 23:25 UTC, each shorter than one 5-minute probe cycle. At least once targon’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 23:25–23:25 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | http 503 |
Was the SambaNova API down on October 29, 2026?
Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:15–06:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
51 single-region failure(s) were also recorded that day (yi-01ai 26, google 7, baichuan 3, doubao 2, sambanova 2, sensenova 2, targon 1, nebius 1, stepfun 1, iflytek 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 28 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0