AI API outages on November 11, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 11, 2026 (UTC) our probes attributed 5 outage(s) to 3 provider(s): Gemini API (Google): 3; baseten API: 1; sensenova API: 1. Providers’ own status pages opened 5 entries (baseten, OpenAI, nebius, replicate).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), baseten API, sensenova API, OpenAI API, nebius API, replicate API · all AI APIs, last 72 hours
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 | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:45–14:05 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥20 min | 3 | provider outage | http 503; timeout |
| 14:25–14:25 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (Santiago) | <5 min | 2 | provider outage | timeout |
| 16:00–16:05 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥4 min | 2 | provider outage | http 503; timeout |
Current Gemini API (Google) status
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 | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 19:00–19:35 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥36 min | 32 | provider outage | [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: |
Self-reported on baseten’s status page, not verified by our probes:
- critical Model APIs are down for all models · resolved Nov 11, 19:38 UTC
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 | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:40–10:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥5 min | 6 | provider outage | timeout |
| 23:10–23:15 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | ≥5 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
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 on OpenAI’s status page, not verified by our probes:
- minor Elevated errors affecting logins, sign-ups, and ChatGPT features · resolved Nov 11, 20:52 UTC
- critical Unable to start new Workspace Agent runs · resolved Nov 12, 08:32 UTC
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 on nebius’s status page, not verified by our probes:
- notice Token Factory connectivity loss in tf-us2 · resolved Nov 11, 13:06 UTC
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 on replicate’s status page, not verified by our probes:
- minor Replicate Model Registry Unavailable · resolved Nov 13, 01:44 UTC
22 single-region failure(s) were also recorded that day (featherless 8, google 5, sambanova 2, baichuan 2, hyperbolic 1, nebius 1, iflytek 1, stepfun 1, friendli 1). A failure seen from one region cannot be separated from a problem on that network path, so none of them is called an outage.
How is an outage told apart from a network problem?
Each provider is probed every five minutes from 4 independent regions. A failure is attributed to the provider only when it is seen from two or more regions at once and no other provider fails in the same minutes; a failure shared with other providers has a cause above all of them and is not blamed on anyone. Durations are lower bounds: we see the first and last failed probe, not the real start and end. Status-page entries are the provider’s own words, shown next to the measurement, not instead of it.
Previous: Nov 10 · Last 72 hours · Next: Nov 12
Machine-readable: incidents.json · Licence: CC BY 4.0