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