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

Yes, measured. 1 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 10:02 UTC, at least 3 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 10:02-10:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 17:02-17:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 17:22-17:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |
| 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 yi-01ai API down on November 1, 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 10:40 UTC, at least 20 minutes observed in total.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 10:40-11:00 | host probes | ap-tokyo sa-east | >=20 min | 4 | provider_outage |

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

## Was the baichuan API down on November 1, 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 |
| --- | --- | --- | --- | --- | --- |
| 05:30-05:35 | host probes | ap-tokyo sa-east us-central | >=5 min | 4 | unattributed |

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

## Was the doubao API down on November 1, 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 |
| --- | --- | --- | --- | --- | --- |
| 23:05-23:05 | 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 1, 2026?

Not attributably. 1 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 |
| --- | --- | --- | --- | --- | --- |
| 05:30-05:40 | host probes | ap-tokyo sa-east us-central | >=10 min | 5 | unattributed |

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

## Was the targon API down on November 1, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 15:52-16:10 | host probes | ap-tokyo eu-hetzner | >=18 min | 3 | unattributed |

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

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