AI API outages on October 13, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 13, 2026 (UTC) our probes attributed 7 outage(s) to 2 provider(s): Gemini API (Google): 6; yi-01ai 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), yi-01ai API, OpenAI API, baichuan API, doubao API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 13, 2026?
Yes, measured. 6 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:40 UTC, at least 6 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 |
|---|---|---|---|---|---|---|
| 06:20–06:20 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 09:20–09:21 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), US (Central) | ≥1 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 10:20–10:20 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503 |
| 12:20–12:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 3 other provider(s) — not attributed | http 503; timeout |
| 12:40–12:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 2 other provider(s) — not attributed | timeout |
| 13:00–13:00 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 13:20–13:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 13:40–13:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 3 other provider(s) — not attributed | http 503; timeout |
| 14:00–14:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 14:20–14:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 4 other provider(s) — not attributed | http 503; timeout |
| 14:40–14:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | provider outage | http 503; timeout |
| 15:00–15:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | provider outage | http 503; timeout |
| 15:20–15:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 15:40–15:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 5 other provider(s) — not attributed | timeout |
| 16:00–16:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 4 other provider(s) — not attributed | http 503; timeout |
| 16:20–16:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | provider outage | timeout |
| 16:40–16:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 17:00–17:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | provider outage | http 503; timeout |
| 17:20–17:21 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 17:40–17:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 18:00–18:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 18:20–18:21 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | provider outage | timeout |
| 18:40–18:41 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | provider outage | http 503; timeout |
Is the Gemini API (Google) down right now? Live status →
Was the yi-01ai API down on October 13, 2026?
Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 06:50 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:50–07:00 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥10 min | 2 | provider outage | timeout |
| 11:25–12:30 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥65 min | 12 | shared with 5 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
Was the OpenAI API down on October 13, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 3 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 Degraded performance in GPT-6.1 Sol Codex and Work mode · resolved Oct 13, 16:36 UTC
Is the OpenAI API down right now? Live status →
Was the baichuan API down on October 13, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 15:21–15:40 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥19 min | 3 | shared with 5 other provider(s) — not attributed | timeout |
Is the baichuan API down right now? Live status →
Was the doubao API down on October 13, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 12:05–12:05 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
55 single-region failure(s) were also recorded that day (yi-01ai 17, baichuan 8, iflytek 7, featherless 5, doubao 4, openai 3, upstage 2, deepinfra 2, google 2, targon 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.
Machine-readable: incidents.json · Licence: CC BY 4.0