AI API outages on October 4, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 4, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): friendli API: 1; yi-01ai API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: friendli API, yi-01ai API, baichuan API, doubao API, stepfun API · all AI APIs, last 72 hours
Was the friendli API down on October 4, 2026?
Yes, measured. 1 outage(s) attributed to friendli: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 02:05 UTC, at least 3 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 02:05–02:07 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥3 min | 3 | provider outage | timeout |
Is the friendli API down right now? Live status →
Was the yi-01ai API down on October 4, 2026?
Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 14:15 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:15–14:15 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
Is the yi-01ai API down right now? Live status →
Was the baichuan API down on October 4, 2026?
Not attributably. 1 multi-region failure(s) of baichuan coincided with failures of other providers, so the cause sat above baichuan and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:30–15:30 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the baichuan API down right now? Live status →
Was the doubao API down on October 4, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 09:50–09:50 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the stepfun API down on October 4, 2026?
Not attributably. 1 multi-region failure(s) of stepfun coincided with failures of other providers, so the cause sat above stepfun and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 11:50–12:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥10 min | 5 | shared with 1 other provider(s) — not attributed | timeout |
Is the stepfun API down right now? Live status →
43 single-region failure(s) were also recorded that day (yi-01ai 15, doubao 5, qwen 4, minimax 4, ernie 3, targon 2, hunyuan 2, google 2, friendli 2, glm 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