AI API outages on August 13, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 13, 2026 (UTC) our probes attributed 3 outage(s) to 2 provider(s): OpenAI API: 2; featherless API: 1. Providers’ own status pages opened 1 entry (Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, featherless API, Claude API (Anthropic), SambaNova API · all AI APIs, last 72 hours
Was the OpenAI API down on August 13, 2026?
Yes, measured. 2 outage(s) attributed to OpenAI: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 20:40 UTC, at least 31 minutes observed in total. OpenAI’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:05–01:20 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥75 min | 14 | shared with 2 other provider(s) — not attributed | timeout |
| 02:00–02:30 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥30 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 03:15–04:10 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥55 min | 9 | shared with 5 other provider(s) — not attributed | timeout |
| 04:30–05:10 | 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 |
| 05:55–06:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 06:20–06:45 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥26 min | 5 | shared with 1 other provider(s) — not attributed | timeout |
| 08:00–09:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥60 min | 11 | shared with 5 other provider(s) — not attributed | timeout |
| 09:15–09:25 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥10 min | 6 | shared with 2 other provider(s) — not attributed | timeout |
| 09:45–09:55 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥10 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 10:15–11:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥95 min | 18 | shared with 3 other provider(s) — not attributed | timeout |
| 12:10–12:15 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 12:30–12:35 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥5 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
| 13:00–13:30 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥30 min | 4 | shared with 3 other provider(s) — not attributed | timeout |
| 13:45–14:35 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥50 min | 11 | shared with 3 other provider(s) — not attributed | timeout |
| 14:55–16:25 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥90 min | 20 | shared with 3 other provider(s) — not attributed | timeout |
| 16:40–17:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 5 | shared with 3 other provider(s) — not attributed | timeout |
| 17:15–18:20 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥64 min | 9 | shared with 3 other provider(s) — not attributed | timeout |
| 18:55–19:30 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥35 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 20:10–20:20 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥10 min | 3 | shared with 2 other provider(s) — not attributed | http 520; timeout |
| 20:40–20:50 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥11 min | 3 | provider outage | timeout |
| 21:10–21:20 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥10 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 21:50–22:10 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥20 min | 4 | provider outage | timeout |
| 22:25–22:50 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥26 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 23:55–00:10 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥15 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
Is the OpenAI API down right now? Live status →
Was the featherless API down on August 13, 2026?
Yes, measured. 1 outage(s) attributed to featherless: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 19:50 UTC, each shorter than one 5-minute probe cycle. At least once featherless’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 19:50–19:50 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | <5 min | 2 | provider outage | http 502 |
Is the featherless API down right now? Live status →
Was the Claude API (Anthropic) down on August 13, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for Claude Mythos 5, Claude Fable 5, and Claude Sonnet 5 · resolved Aug 13, 16:08 UTC
Is the Claude API (Anthropic) down right now? Live status →
Was the SambaNova API down on August 13, 2026?
Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 22:15–22:30 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥16 min | 15 | shared with 1 other provider(s) — not attributed | timeout |
Is the SambaNova API down right now? Live status →
81 single-region failure(s) were also recorded that day (yi-01ai 29, doubao 17, iflytek 14, openai 7, friendli 4, deepinfra 2, google 2, ernie 1, featherless 1, sensenova 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 12 · Last 72 hours · Aug 14 →
Machine-readable: incidents.json · Licence: CC BY 4.0