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

Yes, measured. 10 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 00:42 UTC, at least 36 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 |
| --- | --- | --- | --- | --- | --- |
| 00:42-00:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | provider_outage |
| 01:05-01:05 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | unattributed |
| 08:20-08:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 13:01-13:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 14:01-14:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 14:25-14:25 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | unattributed |
| 14:41-14:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | provider_outage |
| 15:01-15:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | provider_outage |
| 15:21-15:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 15:41-15:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 16:01-16:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 16:21-16:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | unattributed |
| 16:41-16:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east | >=4 min | 3 | provider_outage |
| 17:01-17:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | provider_outage |
| 17:21-17:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east | >=4 min | 3 | provider_outage |
| 17:41-17:45 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | provider_outage |
| 18:01-18:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east | >=4 min | 3 | provider_outage |
| 18:21-18:25 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner sa-east us-central | >=4 min | 4 | provider_outage |
| 18:45-18: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 doubao API down on November 4, 2026?

Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 23:55 UTC, each shorter than one 5-minute probe cycle.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 23:55-23:56 | host probes | ap-tokyo eu-hetzner sa-east | <5 min | 3 | provider_outage |

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

## Was the OpenAI API down on November 4, 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 22:38 UTC: Elevated error rates across paid ChatGPT plans (minor)

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

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