# AI API outages on October 13, 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 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 06:20-06:20 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | unattributed |
| 09:20-09:21 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=1 min | 2 | unattributed |
| 10:20-10:20 | requests to gemini-flash-lite-latest | ap-tokyo us-central | <5 min | 2 | unattributed |
| 12:20-12:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 12:40-12:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 13:00-13:00 | requests to gemini-flash-lite-latest | ap-tokyo us-central | <5 min | 2 | unattributed |
| 13:20-13:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 13:40-13:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 14:00-14:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 14:20-14:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 14:40-14:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 15:00-15:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 15:20-15:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 15:40-15:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 16:00-16:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 16:20-16:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 16:40-16:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 17:00-17:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | provider_outage |
| 17:20-17:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east | <5 min | 3 | unattributed |
| 17:40-17:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | unattributed |
| 18:00-18:01 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | unattributed |
| 18:20-18:21 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | <5 min | 4 | provider_outage |
| 18:40-18:41 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=1 min | 4 | provider_outage |

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

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 06:50-07:00 | host probes | ap-tokyo us-central | >=10 min | 2 | provider_outage |
| 11:25-12:30 | host probes | ap-tokyo us-central | >=65 min | 12 | unattributed |

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

## 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 08:10 UTC: Degraded performance in GPT-6.1 Sol Codex and Work mode (minor)

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

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 15:21-15:40 | host probes | eu-hetzner sa-east | >=19 min | 3 | unattributed |

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

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 12:05-12:05 | host probes | ap-tokyo sa-east us-central | <5 min | 3 | unattributed |

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

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