# AI API outages on October 24, 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 Claude API (Anthropic) down on October 24, 2026?

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic's own status page opened 2 entries that day (self-reported, listed below).
- self-reported 00:31 UTC: Elevated errors for Claude Opus 5.5 (major)
- self-reported 05:16 UTC: Elevated errors for Claude Fable 5 and Claude Fable 5.1 (major)

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

## Was the Gemini API (Google) down on October 24, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:55-15:19 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=24 min | 4 | unattributed |
| 15:57-16:17 | requests to gemini-flash-lite-latest | ap-tokyo sa-east | >=20 min | 3 | unattributed |

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

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

Not attributably. 2 multi-region failure(s) of nebius coincided with failures of other providers, so the cause sat above nebius and is not blamed on it. nebius's own status page opened 1 entry that day (self-reported, listed below).

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 12:12-12:30 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=17 min | 5 | unattributed |
| 12:50-13:43 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=54 min | 16 | unattributed |
- self-reported 13:22 UTC: Token Factory 503 errors in eu-west2 (major)

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

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

Not attributably. 3 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 |
| --- | --- | --- | --- | --- | --- |
| 02:22-02:37 | host probes | ap-tokyo sa-east | >=15 min | 4 | unattributed |
| 13:37-13:42 | host probes | ap-tokyo eu-hetzner | >=5 min | 3 | unattributed |
| 15:17-15:27 | host probes | ap-tokyo sa-east | >=10 min | 2 | unattributed |

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

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