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