AI API outages on October 19, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 19, 2026 (UTC) our probes attributed 10 outage(s) to 5 provider(s): doubao API: 5; Gemini API (Google): 2; stepfun API: 1; writer API: 1; yi-01ai API: 1. Providers’ own status pages opened 1 entry (OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: doubao API, Gemini API (Google), stepfun API, writer API, yi-01ai API, OpenAI API · all AI APIs, last 72 hours
Was the doubao API down on October 19, 2026?
Yes, measured. 5 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 03:50 UTC, at least 39 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:30–01:41 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥11 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 02:06–02:10 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥4 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 03:50–03:56 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥6 min | 2 | provider outage | timeout |
| 05:11–05:15 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥4 min | 2 | provider outage | timeout |
| 06:00–06:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 06:46–07:05 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥19 min | 3 | provider outage | timeout |
| 08:00–08:10 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥10 min | 3 | provider outage | timeout |
| 08:26–08:35 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥9 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 09:45–10:01 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥16 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
| 11:55–12:01 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥6 min | 5 | shared with 2 other provider(s) — not attributed | timeout |
| 12:25–12:36 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥11 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 13:40–14:01 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥21 min | 5 | shared with 4 other provider(s) — not attributed | timeout |
| 14:45–15:05 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥20 min | 4 | shared with 4 other provider(s) — not attributed | timeout |
| 15:56–16:25 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥29 min | 5 | shared with 5 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the Gemini API (Google) down on October 19, 2026?
Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 05:30 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:30–05:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
| 21:00–21:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 21:20–21:20 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | <5 min | 4 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 22:20–22:20 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the stepfun API down on October 19, 2026?
Yes, measured. 1 outage(s) attributed to stepfun: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 23:15 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 23:15–23:15 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
Is the stepfun API down right now? Live status →
Was the writer API down on October 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 05:35 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:35–05:35 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
Is the writer API down right now? Live status →
Was the yi-01ai API down on October 19, 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 00:50 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:50–01:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 2 | provider outage | timeout |
| 13:00–13:30 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥30 min | 5 | shared with 4 other provider(s) — not attributed | timeout |
| 15:25–16:20 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥55 min | 10 | shared with 5 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
Was the OpenAI API down on October 19, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. 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:
- minor File Download errors · resolved Oct 19, 14:14 UTC
Is the OpenAI API down right now? Live status →
92 single-region failure(s) were also recorded that day (yi-01ai 26, doubao 16, stepfun 13, iflytek 10, sensenova 10, google 9, baichuan 5, aleph-alpha 1, fireworks 1, groq 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