AI API outages on November 7, 2026
UTC day · measured every 5 minutes from 4 regions · method
On November 7, 2026 (UTC) our probes attributed 3 outage(s) to 2 provider(s): sensenova API: 2; doubao API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: sensenova API, doubao API · all AI APIs, last 72 hours
Was the sensenova API down on November 7, 2026?
Yes, measured. 2 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 21:10 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 19:05–19:10 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 21:10–21:10 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
| 23:15–23:16 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | provider outage | timeout |
Was the doubao API down on November 7, 2026?
Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 04:40 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 04:40–04:45 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 4 | provider outage | timeout |
16 single-region failure(s) were also recorded that day (iflytek 4, google 3, doubao 3, baichuan 3, aleph-alpha 1, friendli 1, sensenova 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 6 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0