AI API outages on July 29, 2026
UTC day · measured every 5 minutes from 4 regions · method
On July 29, 2026 (UTC) our probes attributed 4 outage(s) to 2 provider(s): Gemini API (Google): 2; yi-01ai API: 2. Providers’ own status pages opened 1 entry (Cerebras).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), yi-01ai API, Cerebras API, doubao API, stepfun API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on July 29, 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 01:45 UTC, at least 8 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:45–01:51 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥7 min | 2 | provider outage | The read operation timed out |
| 12:41–12:56 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥15 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 14:00–14:36 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥37 min | 7 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 15:00–15:01 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥1 min | 2 | shared with 1 other provider(s) — not attributed | The read operation timed out |
| 15:25–15:26 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥1 min | 2 | provider outage | The read operation timed out |
| 16:55–17:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥36 min | 4 | shared with 2 other provider(s) — not attributed | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
Was the yi-01ai API down on July 29, 2026?
Yes, measured. 2 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 06:35 UTC, at least 32 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:35–07:06 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥32 min | 5 | provider outage | timeout |
| 17:35–17:46 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥12 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 18:05–18:05 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
Is the yi-01ai API down right now? Live status →
Was the Cerebras API down on July 29, 2026?
Not by our measurements. No failure of Cerebras was seen from two or more regions at once. Cerebras’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Cerebras’s status page, not verified by our probes:
- minor Partial Service Disruption · resolved Jul 29, 14:14 UTC
Is the Cerebras API down right now? Live status →
Was the doubao API down on July 29, 2026?
Not attributably. 1 multi-region failure(s) of doubao coincided with failures of other providers, so the cause sat above doubao and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 17:30–17:31 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥2 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the stepfun API down on July 29, 2026?
Not attributably. 1 multi-region failure(s) of stepfun coincided with failures of other providers, so the cause sat above stepfun and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 03:20–03:35 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥15 min | 2 | shared with 1 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the stepfun API down right now? Live status →
34 single-region failure(s) were also recorded that day (yi-01ai 13, google 9, iflytek 4, baichuan 2, sambanova 1, doubao 1, deepinfra 1, meta-llama 1, siliconflow 1, nebius 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 28 · Last 72 hours · Jul 30 →
Machine-readable: incidents.json · Licence: CC BY 4.0