# AI API outages on November 11, 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 11, 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 13:45 UTC, at least 24 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 |
| --- | --- | --- | --- | --- | --- |
| 13:45-14:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner | >=20 min | 3 | provider_outage |
| 14:25-14:25 | requests to gemini-flash-lite-latest | ap-tokyo sa-west | <5 min | 2 | provider_outage |
| 16:00-16:05 | requests to gemini-flash-lite-latest | ap-tokyo eu-hetzner | >=4 min | 2 | provider_outage |

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

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

Yes, measured. 1 outage(s) attributed to baseten: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 19:00 UTC, at least 36 minutes observed in total. baseten's own status page opened 1 entry that day (self-reported, listed below).

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 19:00-19:35 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=36 min | 32 | provider_outage |
- self-reported 19:17 UTC: Model APIs are down for all models (critical)

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

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

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 10:40-10:45 | host probes | ap-tokyo eu-hetzner sa-west us-central | >=5 min | 6 | provider_outage |
| 23:10-23:15 | host probes | ap-tokyo sa-west us-central | >=5 min | 4 | unattributed |

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

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

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 2 entries that day (self-reported, listed below).
- self-reported 20:43 UTC: Elevated errors affecting logins, sign-ups, and ChatGPT features (minor)
- self-reported 22:50 UTC: Unable to start new Workspace Agent runs (critical)

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

## Was the nebius API down on November 11, 2026?

Not by our measurements. No failure of nebius was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. nebius's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 13:06 UTC: Token Factory connectivity loss in tf-us2 (none)

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

## Was the replicate API down on November 11, 2026?

Not by our measurements. No failure of replicate was seen from two or more regions at once. replicate's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 04:33 UTC: Replicate Model Registry Unavailable (minor)

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

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