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

Yes, measured. 2 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 03:45 UTC, at least 3 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 03:45-03:45 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | provider_outage |
| 17:22-17:25 | requests to gemini-flash-lite-latest | eu-hetzner sa-east us-central | >=3 min | 3 | unattributed |
| 22:22-22:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |

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

## Was the SambaNova API down on October 31, 2026?

Yes, measured. 1 outage(s) attributed to SambaNova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 01:35 UTC, at least 10 minutes observed in total. SambaNova's status page lists nothing that day.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 01:35-01:45 | host probes | eu-hetzner sa-east us-central | >=10 min | 8 | provider_outage |

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

## Was the nebius API down on October 31, 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 00:38 UTC: Token Factory: some dedicated endpoints partially unavailable (minor)

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

## Was the baichuan API down on October 31, 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 |
| --- | --- | --- | --- | --- | --- |
| 13:15-13:40 | host probes | ap-tokyo eu-hetzner us-central | >=25 min | 3 | unattributed |

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

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