AI API outages on August 26, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 26, 2026 (UTC) our probes attributed 3 outage(s) to 2 provider(s): Gemini API (Google): 2; featherless API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), featherless API, friendli API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on August 26, 2026?
Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 05:30 UTC, at least 13 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:30–05:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | The read operation timed out |
| 09:03–09:15 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥12 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 10:55–10:55 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 2 other provider(s) — not attributed | The read operation timed out |
| 11:45–12:10 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥25 min | 3 | shared with 2 other provider(s) — not attributed | The read operation timed out |
| 13:00–13:00 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 13:25–13:25 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 13:50–14:28 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥38 min | 6 | shared with 2 other provider(s) — not attributed | The read operation timed out |
| 15:43–15:55 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥12 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 17:10–17:23 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥13 min | 3 | provider outage | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
Was the featherless API down on August 26, 2026?
Yes, measured. 1 outage(s) attributed to featherless: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 07:43 UTC, at least 17 minutes observed in total. At least once featherless’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 07:43–08:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥17 min | 16 | provider outage | http 503 |
Is the featherless API down right now? Live status →
Was the friendli API down on August 26, 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 |
|---|---|---|---|---|---|---|
| 20:13–22:10 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥117 min | 96 | shared with 1 other provider(s) — not attributed | http 500 |
Is the friendli API down right now? Live status →
48 single-region failure(s) were also recorded that day (yi-01ai 17, google 9, writer 4, stepfun 4, doubao 3, minimax 2, deepinfra 2, sambanova 2, baichuan 2, hunyuan 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 25 · Last 72 hours · Aug 27 →
Machine-readable: incidents.json · Licence: CC BY 4.0