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