AI API outages on November 9, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 9, 2026 (UTC) our probes attributed 5 outage(s) to 1 provider(s): sensenova API: 5. Providers’ own status pages opened 3 entries (OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: sensenova API, OpenAI API, nebius API · all AI APIs, last 72 hours
Was the sensenova API down on November 9, 2026?
Yes, measured. 5 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 03:25 UTC, at least 9 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 03:25–03:26 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | <5 min | 3 | provider outage | timeout |
| 04:26–04:31 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥5 min | 5 | provider outage | timeout |
| 05:30–05:30 | host probes | 3 of 4: Asia (Tokyo), South America (Santiago), US (Central) | <5 min | 3 | provider outage | timeout |
| 12:30–12:30 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
| 20:42–20:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (Santiago), US (Central) | ≥3 min | 4 | provider outage | timeout |
Was the OpenAI API down on November 9, 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 2 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Elevated ChatGPT Conversation Errors · resolved Nov 9, 19:08 UTC
- minor Elevated Errors On API · resolved Nov 9, 23:50 UTC
Was the nebius API down on November 9, 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 Compute Cloud: some hosts unreachable in eu-north1 · resolved Nov 9, 18:33 UTC
25 single-region failure(s) were also recorded that day (novita 6, iflytek 5, baichuan 4, xai 2, together 2, featherless 1, mistral 1, sambanova 1, stepfun 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 8 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0