AI API outages on September 26, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 26, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): Gemini API (Google): 1; stepfun API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), stepfun API, baichuan API, iflytek API, yi-01ai API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on September 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 11:56 UTC, at least 4 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 11:56–12:00 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥4 min | 2 | provider outage | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the stepfun API down on September 26, 2026?
Yes, measured. 1 outage(s) attributed to stepfun: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 15:30 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:30–15:30 | host probes | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | [Errno 101] Network is unreachable; timeout |
Is the stepfun API down right now? Live status →
Was the baichuan API down on September 26, 2026?
Not attributably. 2 multi-region failure(s) of baichuan coincided with failures of other providers, so the cause sat above baichuan and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 04:55–05:01 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥6 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 12:35–12:50 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥15 min | 3 | shared with 3 other provider(s) — not attributed | timeout |
Is the baichuan API down right now? Live status →
Was the iflytek API down on September 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 |
|---|---|---|---|---|---|---|
| 14:20–14:20 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
Is the iflytek API down right now? Live status →
Was the yi-01ai API down on September 26, 2026?
Not attributably. 4 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 |
|---|---|---|---|---|---|---|
| 04:15–05:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥45 min | 6 | shared with 1 other provider(s) — not attributed | timeout |
| 09:00–09:10 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥10 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 12:20–12:50 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥30 min | 4 | shared with 4 other provider(s) — not attributed | timeout |
| 14:50–15:20 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥30 min | 5 | shared with 2 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
72 single-region failure(s) were also recorded that day (yi-01ai 22, aleph-alpha 14, google 11, iflytek 8, sensenova 5, doubao 5, baichuan 3, stepfun 2, groq 1, hunyuan 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.
Machine-readable: incidents.json · Licence: CC BY 4.0