AI API outages on August 6, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 6, 2026 (UTC) our probes attributed 4 outage(s) to 1 provider(s): OpenAI API: 4.
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, Gemini API (Google), baichuan API, stepfun API, yi-01ai API · all AI APIs, last 72 hours
Was the OpenAI API down on August 6, 2026?
Yes, measured. 4 outage(s) attributed to OpenAI: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 13:40 UTC, at least 36 minutes observed in total. At least once OpenAI’s own host answered with an HTTP 5xx. OpenAI’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:05–01:20 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥15 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 02:00–02:30 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥30 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 05:25–05:30 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 4 | shared with 2 other provider(s) — not attributed | timeout |
| 06:50–06:50 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 09:20–09:35 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥15 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 11:00–11:25 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥25 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 13:40–13:40 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 14:15–14:30 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 15:35–16:10 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥35 min | 8 | shared with 1 other provider(s) — not attributed | timeout |
| 17:15–17:35 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥20 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 18:10–18:20 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥10 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
| 19:05–19:20 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥15 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 19:40–20:30 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥50 min | 9 | shared with 1 other provider(s) — not attributed | timeout |
| 20:50–21:10 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥20 min | 4 | provider outage | http 520; timeout |
| 22:05–22:20 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥15 min | 4 | provider outage | timeout |
| 22:40–22:40 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 23:45–00:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
Is the OpenAI API down right now? Live status →
Was the Gemini API (Google) down on August 6, 2026?
Not attributably. 1 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:30–13:30 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
Was the baichuan API down on August 6, 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 |
|---|---|---|---|---|---|---|
| 06:25–06:25 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
Is the baichuan API down right now? Live status →
Was the stepfun API down on August 6, 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 |
|---|---|---|---|---|---|---|
| 06:45–06:55 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥10 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
Is the stepfun API down right now? Live status →
Was the yi-01ai API down on August 6, 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 |
|---|---|---|---|---|---|---|
| 06:25–06:25 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 10:25–11:30 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥65 min | 8 | shared with 2 other provider(s) — not attributed | timeout |
| 13:55–14:25 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥30 min | 5 | shared with 2 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
73 single-region failure(s) were also recorded that day (openai 21, yi-01ai 18, friendli 12, baichuan 6, iflytek 6, sensenova 3, google 2, sambanova 2, featherless 1, replicate 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.
← Aug 5 · Last 72 hours · Aug 7 →
Machine-readable: incidents.json · Licence: CC BY 4.0