AI API outages on October 8, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 8, 2026 (UTC) our probes attributed 4 outage(s) to 3 provider(s): Gemini API (Google): 2; aleph-alpha API: 1; yi-01ai API: 1. Providers’ own status pages opened 2 entries (OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), aleph-alpha API, yi-01ai API, OpenAI API, TypeSafe API, nebius API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 8, 2026?
Yes, measured. 2 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 3 of 4 regions at once while no other provider was failing, first at 01:30 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:30–01:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | provider outage | timeout |
| 05:50–05:50 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 16:38–18:30 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥112 min | 20 | shared with 31 other provider(s) — not attributed | [Errno 101] Network is unreachable; http 503; timeout |
| 18:50–19:10 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 8 | shared with 38 other provider(s) — not attributed | http 503; timeout |
| 19:30–19:30 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 21:10–21:10 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | <5 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
| 23:50–23:50 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the aleph-alpha API down on October 8, 2026?
Yes, measured. 1 outage(s) attributed to aleph-alpha: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 10:57 UTC, at least 17 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:57–11:15 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥17 min | 6 | provider outage | [Errno 111] Connection refused; [Errno 113] No route to host |
| 11:50–11:57 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥7 min | 8 | shared with 1 other provider(s) — not attributed | timeout |
Is the aleph-alpha API down right now? Live status →
Was the yi-01ai API down on October 8, 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 05:30 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:40–01:40 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
| 05:30–05:30 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 13:17–13:45 | host probes | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥28 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 15:27–15:40 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥13 min | 2 | shared with 11 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the yi-01ai API down right now? Live status →
Was the OpenAI API down on October 8, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 6 single-region failure(s) are not called an outage. OpenAI’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Some APAC users are seeing errors in ChatGPT Work, conversations, and GPTs. · resolved Oct 8, 04:51 UTC
Is the OpenAI API down right now? Live status →
Was the TypeSafe API down on October 8, 2026?
Not attributably. 2 multi-region failure(s) of TypeSafe coincided with failures of other providers, so the cause sat above TypeSafe and is not blamed on it. TypeSafe’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 12:50–12:50 | requests to jev-1.13.0 | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | http 503; timeout |
| 12:50–12:52 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥2 min | 2 | shared with 3 other provider(s) — not attributed | http 503; timeout |
Is the TypeSafe API down right now? Live status →
Was the nebius API down on October 8, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once; 2 single-region failure(s) are not called an outage. nebius’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- minor Metrics unavailable in Management Console for Monitoring in eu-west1 · resolved Oct 8, 08:59 UTC
Is the nebius API down right now? Live status →
Was the iflytek API down on October 8, 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 |
|---|---|---|---|---|---|---|
| 17:33–17:45 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥12 min | 2 | shared with 9 other provider(s) — not attributed | timeout |
Is the iflytek API down right now? Live status →
211 single-region failure(s) were also recorded that day (yi-01ai 19, iflytek 13, hunyuan 11, sensenova 10, cerebras 9, google 8, novita 7, sarvam 7, stepfun 7, baichuan 6). 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