AI API outages on August 14, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 14, 2026 (UTC) our probes attributed 2 outage(s) to 1 provider(s): OpenAI API: 2. Providers’ own status pages opened 4 entries (Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, Claude API (Anthropic), yi-01ai API · all AI APIs, last 72 hours
Was the OpenAI API down on August 14, 2026?
Yes, measured. 2 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:25 UTC, at least 45 minutes observed in total. OpenAI’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:50–01:05 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥15 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 01:25–01:55 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥30 min | 8 | provider outage | timeout |
| 02:20–04:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥145 min | 28 | shared with 3 other provider(s) — not attributed | timeout |
| 05:00–05:30 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥30 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 06:10–06:35 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥25 min | 7 | shared with 5 other provider(s) — not attributed | timeout |
| 07:20–08:10 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥50 min | 10 | shared with 4 other provider(s) — not attributed | timeout |
| 08:40–09:15 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥36 min | 9 | shared with 2 other provider(s) — not attributed | timeout |
| 09:50–11:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥70 min | 10 | shared with 3 other provider(s) — not attributed | timeout |
| 11:45–11:50 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 12:30–12:45 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥15 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
| 13:05–13:25 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥20 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 14:30–16:35 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥126 min | 23 | shared with 6 other provider(s) — not attributed | timeout |
| 17:00–17:00 | host probes | 2 of 4: Europe (Germany), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 17:15–17:30 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥14 min | 3 | provider outage | timeout |
Is the OpenAI API down right now? Live status →
Was the Claude API (Anthropic) down on August 14, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 4 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- minor Service disruption on Claude Code on the web and related services · resolved Aug 14, 00:51 UTC
- notice Issues reaching status.claude.com · resolved Aug 14, 10:53 UTC
- major Service disruption on Claude services · resolved Aug 14, 21:58 UTC
- major Elevated errors for Claude Fable 5 · resolved Aug 15, 00:27 UTC
Is the Claude API (Anthropic) down right now? Live status →
Was the yi-01ai API down on August 14, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 09:05–09: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 |
Is the yi-01ai API down right now? Live status →
82 single-region failure(s) were also recorded that day (yi-01ai 27, doubao 16, iflytek 13, openai 7, friendli 5, google 3, writer 3, hunyuan 2, sambanova 1, cerebras 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 13 · Last 72 hours · Aug 15 →
Machine-readable: incidents.json · Licence: CC BY 4.0