AI API outages on October 14, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 14, 2026 (UTC) our probes attributed 7 outage(s) to 1 provider(s): Gemini API (Google): 7. Providers’ own status pages opened 6 entries (OpenAI, TypeSafe, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), OpenAI API, TypeSafe API, nebius API, doubao API, yi-01ai API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 14, 2026?
Yes, measured. 7 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:40 UTC, at least 4 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:40–00:40 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | http 503; timeout |
| 01:40–01: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 |
| 02:00–02: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 | timeout |
| 02:20–02: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 |
| 13:00–13:01 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥1 min | 2 | provider outage | http 500; timeout |
| 20:00–20:00 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
| 22:40–22:40 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the OpenAI API down on October 14, 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 3 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Degraded performance in Codex and ChatGPT Work · resolved Oct 14, 09:53 UTC
- minor Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst · resolved Oct 14, 10:58 UTC
- minor Delayed Costs data in the Compliance API · resolved — UTC
Is the OpenAI API down right now? Live status →
Was the TypeSafe API down on October 14, 2026?
Not by our measurements. No failure of TypeSafe was seen from two or more regions at once. TypeSafe’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on TypeSafe’s status page, not verified by our probes:
- notice Elevated Latency · resolved Oct 14, 22:52 UTC
Is the TypeSafe API down right now? Live status →
Was the nebius API down on October 14, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- major InfiniBand connectivity issues for GPU clusters in eu-west2 · resolved Oct 14, 10:52 UTC
- minor Connectivity issues between eu-south1 and other Nebius regions · resolved — UTC
Is the nebius API down right now? Live status →
Was the doubao API down on October 14, 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 |
|---|---|---|---|---|---|---|
| 14:30–14:30 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the yi-01ai API down on October 14, 2026?
Not attributably. 1 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:15–14:45 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥30 min | 5 | shared with 6 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
52 single-region failure(s) were also recorded that day (yi-01ai 19, stepfun 6, doubao 4, iflytek 4, sensenova 3, upstage 2, friendli 2, google 2, deepseek 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.
Machine-readable: incidents.json · Licence: CC BY 4.0