AI API outages on November 21, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 21, 2026 (UTC) our probes attributed 4 outage(s) to 2 provider(s): sensenova API: 3; xAI API: 1. Providers’ own status pages opened 1 entry (nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sensenova API, xAI API, nebius API · all AI APIs, last 72 hours
Was the sensenova API down on November 21, 2026?
Yes, measured. 3 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 05:31 UTC, at least 4 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:36–00:38 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥1 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 05:31–05:33 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥1 min | 4 | provider outage | timeout |
| 06:31–06:32 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | <5 min | 3 | provider outage | timeout |
| 23:21–23:23 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥1 min | 4 | provider outage | timeout |
Was the xAI API down on November 21, 2026?
Yes, measured. 1 outage(s) attributed to xAI: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 04:47 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:31–00:43 | host probes | 2 of 4: South America (Santiago), US (Central) | ≥11 min | 2 | shared with 1 other provider(s) — not attributed | http 503 |
| 04:47–04:52 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥5 min | 3 | provider outage | timeout |
Was the nebius API down on November 21, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. 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 Uploads to container registry was not working properly · resolved Nov 21, 08:30 UTC
11 single-region failure(s) were also recorded that day (doubao 4, iflytek 2, baichuan 2, featherless 1, sensenova 1, openai 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 20 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0