AI API outages on November 6, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 6, 2026 (UTC) no AI API outage could be attributed to a provider: nothing failed from two or more regions at once without other providers failing alongside. Providers’ own status pages opened 2 entries (OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, nebius API, doubao API · all AI APIs, last 72 hours
Was the OpenAI API down on November 6, 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 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- notice Elevated error rates with some U.S. business Mastercards · resolved — UTC
Was the nebius API down on November 6, 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:
- critical Network problems · resolved — UTC
Was the doubao API down on November 6, 2026?
Not attributably. 2 multi-region failure(s) of doubao coincided with failures of other providers, so the cause sat above doubao and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:10–14:15 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 4 | shared with 2 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
| 15:05–15:10 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
53 single-region failure(s) were also recorded that day (yi-01ai 33, sambanova 5, friendli 2, sensenova 2, iflytek 2, baichuan 2, openai 1, together 1, google 1, writer 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 5 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0