AI API outages on October 12, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 12, 2026 (UTC) our probes attributed 5 outage(s) to 3 provider(s): SambaNova API: 3; Gemini API (Google): 1; yi-01ai API: 1. Providers’ own status pages opened 2 entries (Groq).
This page is history. Is it down right now?
Live status, updated every 30 minutes: SambaNova API, Gemini API (Google), yi-01ai API, Groq API, doubao API · all AI APIs, last 72 hours
Was the SambaNova API down on October 12, 2026?
Yes, measured. 3 outage(s) attributed to SambaNova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 01:01 UTC, at least 16 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:30–00:45 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥15 min | 5 | shared with 10 other provider(s) — not attributed | timeout |
| 01:01–01:10 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥9 min | 4 | provider outage | timeout |
| 02:20–02:21 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
| 03:45–03:51 | host probes | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥6 min | 5 | provider outage | timeout |
Is the SambaNova API down right now? Live status →
Was the Gemini API (Google) down on October 12, 2026?
Yes, measured. 1 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 07:00 UTC, at least 1 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 |
|---|---|---|---|---|---|---|
| 07:00–07:01 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥1 min | 4 | provider outage | http 503; timeout |
Is the Gemini API (Google) down right now? Live status →
Was the yi-01ai API down on October 12, 2026?
Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 13:26 UTC, at least 4 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:50–13:05 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥15 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 13:26–13:30 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥4 min | 2 | provider outage | timeout |
Is the yi-01ai API down right now? Live status →
Was the Groq API down on October 12, 2026?
Not by our measurements. No failure of Groq was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. Groq’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on Groq’s status page, not verified by our probes:
- minor GroqCloud Console Errors Affecting Multiple Regions · resolved Oct 12, 04:00 UTC
- major Model Performance or Availability Issue · resolved Oct 12, 18:36 UTC
Is the Groq API down right now? Live status →
Was the doubao API down on October 12, 2026?
Not attributably. 1 multi-region failure(s) of doubao coincided with failures of other providers, so the cause sat above doubao and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:55–13:55 | 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 doubao API down right now? Live status →
49 single-region failure(s) were also recorded that day (yi-01ai 15, baichuan 5, featherless 3, google 3, iflytek 3, deepinfra 2, doubao 2, nscale 1, openai 1, sambanova 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