# AI API outages on October 7, 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 7, 2026?

Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 05:37 UTC, at least 12 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 05:37-05:50 | requests to gemini-flash-lite-latest | eu-hetzner us-central | >=12 min | 2 | provider_outage |
| 14:10-14:10 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |
| 14:57-15:17 | requests to gemini-flash-lite-latest | eu-hetzner sa-east us-central | >=20 min | 4 | unattributed |
| 21:10-21:30 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=20 min | 7 | unattributed |

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

## Was the OpenAI API down on October 7, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 5 entries that day (self-reported, listed below).
- self-reported 01:12 UTC: Workspace Agents Degraded and Responses Impacted (minor)
- self-reported 05:31 UTC: Unable to create new ChatGPT Work threads in latest version of desktop app (major)
- self-reported 16:31 UTC: Dot in Codex may fail to create new threads (minor)
- self-reported 17:21 UTC: Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and red (minor)
- self-reported 23:42 UTC: Elevated errors with GPT-5.6 Instant in FedRAMP workspaces (minor)

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

## Was the Claude API (Anthropic) down on October 7, 2026?

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic's own status page opened 3 entries that day (self-reported, listed below).
- self-reported 01:20 UTC: Elevated errors loading usage data on platform.claude.com (major)
- self-reported 13:25 UTC: Elevated errors on platform.claude.com (major)
- self-reported 21:23 UTC: Issue with spend limits (none)

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

## Was the nebius API down on October 7, 2026?

Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 17:10 UTC: Problems with power for several dozens of nodes (major)

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

## Was the baichuan API down on October 7, 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 |
| --- | --- | --- | --- | --- | --- |
| 10:55-11:00 | host probes | sa-east us-central | >=5 min | 3 | unattributed |

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

## Was the doubao API down on October 7, 2026?

Not attributably. 2 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 |
| --- | --- | --- | --- | --- | --- |
| 03:05-03:15 | host probes | sa-east us-central | >=10 min | 3 | unattributed |
| 10:50-10:55 | host probes | ap-tokyo sa-east | >=5 min | 2 | unattributed |

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

## Was the iflytek API down on October 7, 2026?

Not attributably. 1 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 01:10-01:17 | host probes | eu-hetzner sa-east | >=8 min | 2 | unattributed |

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

## Was the yi-01ai API down on October 7, 2026?

Not attributably. 4 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 |
| --- | --- | --- | --- | --- | --- |
| 04:45-05:10 | host probes | ap-tokyo sa-east | >=25 min | 4 | unattributed |
| 10:20-10:20 | host probes | ap-tokyo sa-east | <5 min | 2 | unattributed |
| 12:47-13:00 | host probes | ap-tokyo eu-hetzner | >=13 min | 2 | unattributed |
| 15:30-16:00 | host probes | ap-tokyo sa-east | >=30 min | 4 | unattributed |

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

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