AI API outages on October 7, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 7, 2026 (UTC) our probes attributed 2 outage(s) to 1 provider(s): Gemini API (Google): 2. Providers’ own status pages opened 9 entries (OpenAI, Anthropic, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), OpenAI API, Claude API (Anthropic), nebius API, baichuan API, doubao API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 7, 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 05:37 UTC, at least 12 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 05:37–05:50 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), US (Central) | ≥12 min | 2 | provider outage | timeout |
| 14:10–14:10 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | provider outage | timeout |
| 14:57–15:17 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 4 | shared with 1 other provider(s) — not attributed | timeout |
| 21:10–21:30 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥20 min | 7 | shared with 2 other provider(s) — not attributed | http 503; timeout |
Is the Gemini API (Google) down right now? Live status →
Was the OpenAI API down on October 7, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI’s own status page opened 5 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Workspace Agents Degraded and Responses Impacted · resolved Oct 7, 03:00 UTC
- major Unable to create new ChatGPT Work threads in latest version of desktop app · resolved Oct 7, 11:53 UTC
- minor Dot in Codex may fail to create new threads · resolved Oct 7, 18:06 UTC
- minor Degraded performance in Codex and Work mode: Dot turn failures, delayed responses, and red · resolved Oct 7, 18:23 UTC
- minor Elevated errors with GPT-5.6 Instant in FedRAMP workspaces · resolved Oct 8, 00:03 UTC
Is the OpenAI API down right now? Live status →
Was the Claude API (Anthropic) down on October 7, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors loading usage data on platform.claude.com · resolved Oct 7, 02:33 UTC
- major Elevated errors on platform.claude.com · resolved — UTC
- notice Issue with spend limits · resolved Oct 7, 21:23 UTC
Is the Claude API (Anthropic) down right now? Live status →
Was the nebius API down on October 7, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. 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:
- major Problems with power for several dozens of nodes · resolved — UTC
Is the nebius API down right now? Live status →
Was the baichuan API down on October 7, 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 |
|---|---|---|---|---|---|---|
| 10:55–11:00 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥5 min | 3 | shared with 5 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the baichuan API down right now? Live status →
Was the doubao API down on October 7, 2026?
Not attributably. 2 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 |
|---|---|---|---|---|---|---|
| 03:05–03:15 | host probes | 2 of 4: South America (São Paulo), US (Central) | ≥10 min | 3 | shared with 5 other provider(s) — not attributed | timeout |
| 10:50–10:55 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥5 min | 2 | shared with 5 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the iflytek API down on October 7, 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 |
|---|---|---|---|---|---|---|
| 01:10–01:17 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥8 min | 2 | shared with 4 other provider(s) — not attributed | [Errno 104] Connection reset by peer; timeout |
Is the iflytek API down right now? Live status →
Was the yi-01ai API down on October 7, 2026?
Not attributably. 4 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 04:45–05:10 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥25 min | 4 | shared with 4 other provider(s) — not attributed | timeout |
| 10:20–10: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 |
| 12:47–13:00 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥13 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
| 15:30–16:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥30 min | 4 | shared with 3 other provider(s) — not attributed | [Errno 101] Network is unreachable; timeout |
Is the yi-01ai API down right now? Live status →
83 single-region failure(s) were also recorded that day (sensenova 15, iflytek 13, stepfun 12, yi-01ai 12, doubao 11, google 10, baichuan 4, hunyuan 2, writer 1, xai 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