AI API outages on October 17, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 17, 2026 (UTC) our probes attributed 3 outage(s) to 1 provider(s): doubao API: 3.
This page is history. Is it down right now?
Live status, updated every 30 minutes: doubao API, yi-01ai API · all AI APIs, last 72 hours
Was the doubao API down on October 17, 2026?
Yes, measured. 3 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 06:53 UTC, at least 32 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:53–06:55 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥2 min | 3 | provider outage | timeout |
| 07:35–07:45 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 3 | provider outage | timeout |
| 16:20–16:40 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥20 min | 3 | provider outage | timeout |
Is the doubao API down right now? Live status →
Was the yi-01ai API down on October 17, 2026?
Not attributably. 3 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:35–01:35 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
| 04:05–04:10 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 10:50–11:05 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
67 single-region failure(s) were also recorded that day (yi-01ai 18, doubao 12, stepfun 10, iflytek 8, sensenova 8, baichuan 5, kimi 2, sambanova 2, aleph-alpha 1, fireworks 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.
Machine-readable: incidents.json · Licence: CC BY 4.0