AI API outages on September 21, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 21, 2026 (UTC) our probes attributed 9 outage(s) to 2 provider(s): featherless API: 6; Gemini API (Google): 3. Providers’ own status pages opened 4 entries (TypeSafe, baseten).
This page is history. Is it down right now?
Live status, updated every 30 minutes: featherless API, Gemini API (Google), TypeSafe API, baseten API, iflytek API, minimax API · all AI APIs, last 72 hours
Was the featherless API down on September 21, 2026?
Yes, measured. 6 outage(s) attributed to featherless: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 01:53 UTC, at least 69 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:53–01:55 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥2 min | 2 | provider outage | timeout |
| 03:20–03:20 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
| 03:40–04:10 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥30 min | 7 | shared with 1 other provider(s) — not attributed | timeout |
| 04:50–04:55 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 05:23–06:00 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥37 min | 8 | provider outage | timeout |
| 09:00–09:15 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 10:03–10:05 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥2 min | 2 | provider outage | timeout |
| 10:25–10:38 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥13 min | 2 | provider outage | timeout |
| 12:05–12:20 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥15 min | 2 | provider outage | timeout |
| 14:13–14:25 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥12 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 16:25–16:45 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥20 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 18:05–19:55 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥110 min | 28 | shared with 2 other provider(s) — not attributed | timeout |
Current featherless API status
Was the Gemini API (Google) down on September 21, 2026?
Yes, measured. 3 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 4 of 4 regions at once while no other provider was failing, first at 01:15 UTC, at least 6 minutes observed in total. At least once Google’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:15–01:18 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | provider outage | http 503; timeout |
| 14:15–14:18 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥3 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
| 14:35–14:35 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 14:55–14:58 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | provider outage | timeout |
| 15:15–15:18 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 19:15–19:15 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
Current Gemini API (Google) status
Was the TypeSafe API down on September 21, 2026?
Not by our measurements. No failure of TypeSafe was seen from two or more regions at once. TypeSafe’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on TypeSafe’s status page, not verified by our probes:
- notice Console is unavailable. · resolved Sep 29, 22:05 UTC
- notice API issues · resolved Sep 21, 23:40 UTC
Was the baseten API down on September 21, 2026?
Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on baseten’s status page, not verified by our probes:
- minor Metrics degradation in UI and API. **Inference not affected** · resolved Sep 21, 13:42 UTC
- major Elevated inference 500s for a subset of models deployed in GCP central1 · resolved Sep 21, 18:41 UTC
Was the iflytek API down on September 21, 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:03–14:05 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥2 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
Was the minimax API down on September 21, 2026?
Not attributably. 1 multi-region failure(s) of minimax coincided with failures of other providers, so the cause sat above minimax and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:10–13:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
39 single-region failure(s) were also recorded that day (featherless 8, google 5, nebius 4, hunyuan 4, qwen 3, sambanova 3, aleph-alpha 2, minimax 2, openrouter 2, openai 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 20 · Last 72 hours · Next: Sep 22
Machine-readable: incidents.json · Licence: CC BY 4.0