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

Yes, measured. 4 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 09:22 UTC, at least 11 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:22-09:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 09:42-09:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 12:02-12:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 13:02-13:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner us-central | >=3 min | 3 | unattributed |
| 14:02-14:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 17:42-17:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 19:42-19:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 22:02-22:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |

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

## Was the SambaNova API down on November 2, 2026?

Not attributably. 2 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova's status page lists nothing that day.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 06:05-06:17 | host probes | eu-hetzner sa-east us-central | >=12 min | 3 | unattributed |
| 12:15-12:15 | host probes | sa-east us-central | <5 min | 2 | unattributed |

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

## Was the nebius API down on November 2, 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 09:09 UTC: Public API gateway partially unavailable in US-NORTH1 and US-CENTRAL1 (minor)

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

## Was the baichuan API down on November 2, 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 |
| --- | --- | --- | --- | --- | --- |
| 12:20-12:20 | host probes | sa-east us-central | <5 min | 2 | unattributed |

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

Source: https://llmlatency.dev/incidents/2026-11-02 · CC BY 4.0