# AI API outages on October 14, 2026 (UTC)

Measured every 5 minutes from 4 regions. An outage is attributed to a provider only when it failed from 2+ regions at once and no other provider failed in the same minutes.

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:40-00:40 | requests to gemini-flash-lite-latest | ap-tokyo sa-east | <5 min | 2 | provider_outage |
| 01:40-01:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | provider_outage |
| 02:00-02:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 02:20-02:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 13:00-13:01 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=1 min | 2 | provider_outage |
| 20:00-20:00 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage |
| 22:40-22:40 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |

Live status now: https://llmlatency.dev/provider/google

## 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 07:05 UTC: Degraded performance in Codex and ChatGPT Work (minor)
- self-reported 10:18 UTC: Limited availability on gpt-image-2.5-flare and gpt-image-2.5-sunburst (minor)
- self-reported 17:00 UTC: Delayed Costs data in the Compliance API (minor)

Live status now: https://llmlatency.dev/provider/openai

## 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 22:07 UTC: Elevated Latency (none)

Live status now: https://llmlatency.dev/provider/typesafe

## 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 09:54 UTC: InfiniBand connectivity issues for GPU clusters in eu-west2 (major)
- self-reported 20:41 UTC: Connectivity issues between eu-south1 and other Nebius regions (minor)

Live status now: https://llmlatency.dev/provider/nebius

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:30-14:30 | host probes | ap-tokyo sa-east | <5 min | 2 | unattributed |

Live status now: https://llmlatency.dev/provider/doubao

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:15-14:45 | host probes | ap-tokyo sa-east | >=30 min | 5 | unattributed |

Live status now: https://llmlatency.dev/provider/yi-01ai

Source: https://llmlatency.dev/incidents/2026-10-14 · CC BY 4.0