AI API outages on August 29, 2026
UTC day · measured every 5 minutes from 4 regions · method
On August 29, 2026 (UTC) no AI API outage could be attributed to a provider: nothing failed from two or more regions at once without other providers failing alongside.
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 29, 2026?
Not attributably. 1 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:25–13:25 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
49 single-region failure(s) were also recorded that day (google 20, yi-01ai 20, sambanova 3, iflytek 2, friendli 1, doubao 1, hunyuan 1, nscale 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 28 · Last 72 hours · Aug 30 →
Machine-readable: incidents.json · Licence: CC BY 4.0