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 3 outage(s) to 3 provider(s): Gemini API (Google): 1; baichuan API: 1; stepfun API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), baichuan API, stepfun API, iflytek 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 |
Current Gemini API (Google) status
Was the baichuan API down on September 26, 2026?
Yes, measured. 1 outage(s) attributed to baichuan: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 04:55 UTC, at least 6 minutes observed in total.
| 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 | provider outage | timeout |
| 12:35–12:50 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥15 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
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 |
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 1 other provider(s) — not attributed | timeout |
50 single-region failure(s) were also recorded that day (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.
Previous: Sep 25 · Last 72 hours · Next: Sep 27
Machine-readable: incidents.json · Licence: CC BY 4.0