AI API outages on July 26, 2026
UTC day · measured every 5 minutes from 4 regions · method
On July 26, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): Gemini API (Google): 1; doubao API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), doubao API, iflytek API, stepfun API, yi-01ai API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on July 26, 2026?
Yes, measured. 1 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 18:13 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 18:13–18:13 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | The read operation timed out |
Is the Gemini API (Google) down right now? Live status →
Was the doubao API down on July 26, 2026?
Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 08:22 UTC, at least 13 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 08:22–08:35 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥13 min | 3 | provider outage | timeout |
| 13:25–13:33 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥9 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the iflytek API down on July 26, 2026?
Not attributably. 1 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 09:01–09:16 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥16 min | 3 | shared with 2 other provider(s) — not attributed | [Errno 104] Connection reset by peer; timeout |
Is the iflytek API down right now? Live status →
Was the stepfun API down on July 26, 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 |
|---|---|---|---|---|---|---|
| 16:46–16:51 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥5 min | 3 | shared with 3 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the stepfun API down right now? Live status →
Was the yi-01ai API down on July 26, 2026?
Not attributably. 2 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:26–15:31 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
| 16:46–16:51 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
56 single-region failure(s) were also recorded that day (iflytek 8, stepfun 7, nebius 5, yi-01ai 5, baichuan 4, doubao 4, sambanova 3, deepinfra 3, sensenova 3, google 3). 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 25 · Last 72 hours · Jul 27 →
Machine-readable: incidents.json · Licence: CC BY 4.0