# AI API outages on November 20, 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 20, 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 14:01 UTC, at least 2 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 14:01-14:02 | requests to gemini-flash-lite-latest | eu-hetzner us-central | <5 min | 2 | provider_outage |
| 15:01-15:02 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner us-central | <5 min | 3 | provider_outage |

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

## Was the sensenova API down on November 20, 2026?

Yes, measured. 2 outage(s) attributed to sensenova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 22:41 UTC, at least 1 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:06-00:07 | host probes | ap-tokyo us-central | <5 min | 2 | unattributed |
| 06:01-06:03 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=1 min | 4 | unattributed |
| 09:56-09:57 | host probes | ap-tokyo eu-hetzner us-central | <5 min | 3 | unattributed |
| 22:41-22:42 | host probes | ap-tokyo us-central | <5 min | 2 | provider_outage |
| 23:41-23:42 | host probes | ap-tokyo eu-hetzner us-central | <5 min | 3 | provider_outage |

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

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

Not attributably. 2 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 |
| --- | --- | --- | --- | --- | --- |
| 04:01-04:03 | host probes | sa-west us-central | >=1 min | 2 | unattributed |
| 05:18-05:32 | host probes | ap-tokyo eu-hetzner sa-west | >=15 min | 3 | unattributed |

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

## Was the doubao API down on November 20, 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 |
| --- | --- | --- | --- | --- | --- |
| 06:01-06:27 | host probes | ap-tokyo eu-hetzner us-central | >=25 min | 4 | unattributed |
| 08:06-08:07 | host probes | ap-tokyo us-central | <5 min | 2 | unattributed |

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

## Was the iflytek API down on November 20, 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 |
| --- | --- | --- | --- | --- | --- |
| 03:53-04:08 | host probes | ap-tokyo sa-west | >=15 min | 3 | unattributed |
| 04:42-04:43 | host probes | sa-west us-central | >=1 min | 2 | unattributed |
| 06:12-06:23 | host probes | ap-tokyo sa-west | >=11 min | 2 | unattributed |
| 08:33-08:42 | host probes | ap-tokyo sa-west | >=9 min | 2 | unattributed |

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

## Was the siliconflow API down on November 20, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:53-10:43 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=50 min | 41 | unattributed |

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

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