AI API outages on August 23, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 23, 2026 (UTC) our probes attributed 2 outage(s) to 1 provider(s): Gemini API (Google): 2.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google) · all AI APIs, last 72 hours
Was the Gemini API (Google) down on August 23, 2026?
Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 13:35 UTC, at least 2 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:35–13:35 | 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 |
| 20:38–20:40 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), US (Central) | ≥2 min | 2 | provider outage | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
76 single-region failure(s) were also recorded that day (yi-01ai 22, cohere 14, nscale 14, baseten 9, google 5, sambanova 3, friendli 2, nebius 2, iflytek 1, doubao 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 22 · Last 72 hours · Aug 24 →
Machine-readable: incidents.json · Licence: CC BY 4.0