AI API outages on September 19, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 19, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): writer API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: writer API, doubao API, iflytek API, stepfun API, yi-01ai API · all AI APIs, last 72 hours
Was the writer API down on September 19, 2026?
Yes, measured. 1 outage(s) attributed to writer: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 21:48 UTC, at least 7 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 21:48–21:55 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥7 min | 2 | provider outage | timeout |
Is the writer API down right now? Live status →
Was the doubao API down on September 19, 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 |
|---|---|---|---|---|---|---|
| 13:48–14:00 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥12 min | 2 | shared with 5 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the iflytek API down on September 19, 2026?
Not attributably. 1 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:00–14:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 4 other provider(s) — not attributed | timeout |
Is the iflytek API down right now? Live status →
Was the stepfun API down on September 19, 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 |
|---|---|---|---|---|---|---|
| 12:40–13:10 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥30 min | 3 | shared with 2 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the stepfun API down right now? Live status →
Was the yi-01ai API down on September 19, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 14:00–14:00 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 4 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
38 single-region failure(s) were also recorded that day (yi-01ai 11, nebius 4, cerebras 4, google 3, sensenova 3, deepinfra 2, baichuan 2, stepfun 2, sambanova 2, doubao 2). 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.
← Sep 18 · Last 72 hours · Sep 20 →
Machine-readable: incidents.json · Licence: CC BY 4.0