AI API outages on November 19, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 19, 2026 (UTC) our probes attributed 6 outage(s) to 2 provider(s): sensenova API: 5; Gemini API (Google): 1. Providers’ own status pages opened 3 entries (Anthropic, OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sensenova API, Gemini API (Google), Claude API (Anthropic), OpenAI API, nebius API, featherless API · all AI APIs, last 72 hours
Was the sensenova API down on November 19, 2026?
Yes, measured. 5 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 00:35 UTC, at least 2 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:35–00:35 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 07:25–07:25 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 10:20–10:20 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 12:40–12:40 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 18:18–18:20 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago) | ≥2 min | 3 | provider outage | timeout |
Was the Gemini API (Google) down on November 19, 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 17:00 UTC, at least 3 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:20–05:23 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 08:40–08:40 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 15:00–15:03 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (Santiago) | ≥3 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 15:40–15:43 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥4 min | 4 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 16:00–16:03 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 16:20–16:23 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), US (Central) | ≥4 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 16:40–16:43 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥3 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 17:00–17:03 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥3 min | 4 | provider outage | timeout |
Current Gemini API (Google) status
Was the Claude API (Anthropic) down on November 19, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for Claude Mythos 5.2 and Claude Fable 5.2 · resolved Nov 19, 09:33 UTC
Current Claude API (Anthropic) status
Was the OpenAI API down on November 19, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- major Elevated error rates for gpt-6 Luna API requests · resolved Nov 19, 16:58 UTC
Was the nebius API down on November 19, 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:
- major Token Factory: errors on GLM-5.2 model requests in us-central1 · resolved — UTC
Was the featherless API down on November 19, 2026?
Not attributably. 1 multi-region failure(s) of featherless coincided with failures of other providers, so the cause sat above featherless and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:48–15:20 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥32 min | 28 | shared with 4 other provider(s) — not attributed | http 502; timeout |
Current featherless API status
42 single-region failure(s) were also recorded that day (google 11, sambanova 8, doubao 5, iflytek 5, friendli 3, baichuan 3, siliconflow 1, nebius 1, writer 1, stepfun 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 18 · Last 72 hours · Next: Nov 20
Machine-readable: incidents.json · Licence: CC BY 4.0