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

Yes, measured. 3 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 07:45 UTC, at least 4 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 |
| --- | --- | --- | --- | --- | --- |
| 03:41-03:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner | >=4 min | 2 | unattributed |
| 07:45-07:45 | requests to gemini-flash-lite-latest | sa-east us-central | <5 min | 2 | provider_outage |
| 08:01-08:05 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=4 min | 2 | provider_outage |
| 13:01-13:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner us-central | >=4 min | 3 | unattributed |
| 17:45-17:45 | requests to gemini-flash-lite-latest | ap-tokyo sa-east | <5 min | 2 | provider_outage |

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

## Was the yi-01ai API down on November 5, 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 16:40 UTC, at least 5 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 16:40-16:45 | host probes | ap-tokyo sa-east | >=5 min | 2 | provider_outage |

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

## Was the OpenAI API down on November 5, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 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 15:25 UTC: ChatGPT Work and Dots Errors (minor)

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

## Was the baseten API down on November 5, 2026?

Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 21:35 UTC: Elevated errors for Kimi-K3 on Model APIs. **Dedicated Inference is not affected** (minor)

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

## Was the nebius API down on November 5, 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 10:30 UTC: Token Factory: some models unavailable in eu-north1 (major)

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

## Was the baichuan API down on November 5, 2026?

Not attributably. 3 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 |
| --- | --- | --- | --- | --- | --- |
| 00:40-01:15 | host probes | sa-east us-central | >=35 min | 4 | unattributed |
| 04:20-04:20 | host probes | sa-east us-central | <5 min | 2 | unattributed |
| 18:55-18:55 | host probes | sa-east us-central | <5 min | 2 | unattributed |

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

## Was the doubao API down on November 5, 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 |
| --- | --- | --- | --- | --- | --- |
| 05:25-05:26 | host probes | eu-hetzner sa-east us-central | <5 min | 3 | unattributed |

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

## Was the ernie API down on November 5, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 11:40-11:50 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=11 min | 7 | unattributed |

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

## Was the iflytek API down on November 5, 2026?

Not attributably. 4 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:05-01:15 | host probes | sa-east us-central | >=10 min | 4 | unattributed |
| 02:10-02:35 | host probes | sa-east us-central | >=25 min | 3 | unattributed |
| 03:45-03:45 | host probes | sa-east us-central | <5 min | 2 | unattributed |
| 18:55-18:55 | host probes | sa-east us-central | <5 min | 2 | unattributed |

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

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