AI API outages on July 28, 2026
UTC day · measured every 5 minutes from 4 regions · method
On July 28, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): Cerebras API: 1; Gemini API (Google): 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Cerebras API, Gemini API (Google) · all AI APIs, last 72 hours
Was the Cerebras API down on July 28, 2026?
Yes, measured. 1 outage(s) attributed to Cerebras: requests to gpt-oss-120b failed from up to 2 of 4 regions at once while no other provider was failing, first at 03:26 UTC, at least 14 minutes observed in total. Cerebras’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 03:26–03:40 | requests to gpt-oss-120b | 2 of 4: Europe (Germany), US (Central) | ≥14 min | 2 | provider outage | The read operation timed out |
| 18:15–18:40 | requests to gpt-oss-120b | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥25 min | 6 | shared with 1 other provider(s) — not attributed | http 503 |
Is the Cerebras API down right now? Live status →
Was the Gemini API (Google) down on July 28, 2026?
Yes, measured. 1 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 14:25 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:31–12:56 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥25 min | 4 | shared with 2 other provider(s) — not attributed | The read operation timed out |
| 14:25–14:30 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 3 | provider outage | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
43 single-region failure(s) were also recorded that day (google 21, sensenova 3, iflytek 2, stepfun 2, sambanova 1, deepinfra 1, sarvam 1, baichuan 1, nebius 1, yi-01ai 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.
← Jul 27 · Last 72 hours · Jul 29 →
Machine-readable: incidents.json · Licence: CC BY 4.0