AI API outages on September 12, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 12, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): SambaNova API: 1.
This page is history. Is it down right now?
Live status, updated every 30 minutes: SambaNova API, Gemini API (Google), baichuan API, iflytek API · all AI APIs, last 72 hours
Was the SambaNova API down on September 12, 2026?
Yes, measured. 1 outage(s) attributed to SambaNova: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 10:16 UTC, at least 8 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:16–10:23 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥8 min | 2 | provider outage | timeout |
| 15:01–15:06 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥5 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
Is the SambaNova API down right now? Live status →
Was the Gemini API (Google) down on September 12, 2026?
Not attributably. 1 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:58–15:01 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥2 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
Is the Gemini API (Google) down right now? Live status →
Was the baichuan API down on September 12, 2026?
Not attributably. 1 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 |
|---|---|---|---|---|---|---|
| 22:17–22:27 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥10 min | 4 | shared with 2 other provider(s) — not attributed | timeout |
Is the baichuan API down right now? Live status →
Was the iflytek API down on September 12, 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 |
|---|---|---|---|---|---|---|
| 22:11–22:26 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥14 min | 2 | shared with 3 other provider(s) — not attributed | [Errno 113] No route to host; timeout |
Is the iflytek API down right now? Live status →
39 single-region failure(s) were also recorded that day (yi-01ai 20, google 5, siliconflow 2, openai 2, doubao 1, baichuan 1, sensenova 1, deepinfra 1, nebius 1, iflytek 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.
← Sep 11 · Last 72 hours · Sep 13 →
Machine-readable: incidents.json · Licence: CC BY 4.0