AI API outages on August 10, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 10, 2026 (UTC) our probes attributed 8 outage(s) to 1 provider(s): OpenAI API: 8.
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, doubao API · all AI APIs, last 72 hours
Was the OpenAI API down on August 10, 2026?
Yes, measured. 8 outage(s) attributed to OpenAI: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 01:05 UTC, at least 150 minutes observed in total. OpenAI’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:40–00:40 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 01:05–01:30 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥25 min | 5 | provider outage | timeout |
| 02:30–03:05 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥35 min | 6 | provider outage | timeout |
| 03:20–03:35 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥15 min | 3 | provider outage | timeout |
| 03:55–04:35 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥40 min | 9 | shared with 3 other provider(s) — not attributed | timeout |
| 05:30–06:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥30 min | 7 | shared with 1 other provider(s) — not attributed | timeout |
| 06:15–06:35 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 7 | shared with 1 other provider(s) — not attributed | timeout |
| 07:05–07:35 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥30 min | 7 | shared with 1 other provider(s) — not attributed | timeout |
| 08:10–09:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥50 min | 12 | shared with 4 other provider(s) — not attributed | timeout |
| 09:30–09:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 5 | provider outage | timeout |
| 10:15–10:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥35 min | 9 | shared with 1 other provider(s) — not attributed | timeout |
| 11:35–12:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥75 min | 15 | shared with 2 other provider(s) — not attributed | timeout |
| 13:20–13:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥30 min | 9 | shared with 1 other provider(s) — not attributed | timeout |
| 14:15–14:20 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥5 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 15:05–15:10 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 15:30–15:55 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥25 min | 5 | shared with 1 other provider(s) — not attributed | timeout |
| 16:25–17:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥35 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 17:20–17:25 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥5 min | 2 | provider outage | timeout |
| 18:05–18:15 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥10 min | 2 | provider outage | timeout |
| 18:30–18:30 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | <5 min | 2 | provider outage | timeout |
| 18:50–18: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 |
| 19:15–20:05 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥50 min | 8 | shared with 2 other provider(s) — not attributed | timeout |
| 20:50–21:30 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥40 min | 7 | provider outage | timeout |
| 22:45–23:20 | 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 |
| 23:35–00:15 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥40 min | 10 | shared with 2 other provider(s) — not attributed | timeout |
Is the OpenAI API down right now? Live status →
Was the doubao API down on August 10, 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 |
|---|---|---|---|---|---|---|
| 19:45–19:45 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
41 single-region failure(s) were also recorded that day (yi-01ai 16, openai 7, friendli 5, iflytek 4, google 2, writer 1, cohere 1, sensenova 1, deepinfra 1, sambanova 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 9 · Last 72 hours · Aug 11 →
Machine-readable: incidents.json · Licence: CC BY 4.0