HomeIncidents
Data API

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.

UTCWhat failedRegionsDurationFailed probesVerdictError
05:37–05:50requests to gemini-flash-lite-latest2 of 4: Europe (Germany), US (Central)≥12 min2provider outagetimeout
14:10–14:10requests to gemini-flash-lite-latest3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)<5 min3provider outagetimeout
14:57–15:17requests to gemini-flash-lite-latest3 of 4: Europe (Germany), South America (São Paulo), US (Central)≥20 min4shared with 1 other provider(s) — not attributedtimeout
21:10–21:30requests to gemini-flash-lite-latest4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥20 min7shared with 1 other provider(s) — not attributedhttp 503; timeout

Current Gemini API (Google) 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

Current OpenAI API 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:

Current Claude API (Anthropic) 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:

Current nebius API 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.

UTCWhat failedRegionsDurationFailed probesVerdictError
10:55–11:00host probes2 of 4: South America (São Paulo), US (Central)≥5 min3shared with 4 other provider(s) — not attributed[Errno 101] Network is unreachable; timeout

Current baichuan API 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.

UTCWhat failedRegionsDurationFailed probesVerdictError
03:05–03:15host probes2 of 4: South America (São Paulo), US (Central)≥10 min3shared with 4 other provider(s) — not attributedtimeout
10:50–10:55host probes2 of 4: Asia (Tokyo), South America (São Paulo)≥5 min2shared with 4 other provider(s) — not attributedtimeout

Current doubao API 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.

UTCWhat failedRegionsDurationFailed probesVerdictError
01:10–01:17host probes2 of 4: Europe (Germany), South America (São Paulo)≥8 min2shared with 3 other provider(s) — not attributed[Errno 104] Connection reset by peer; timeout

Current iflytek API status

69 single-region failure(s) were also recorded that day (sensenova 15, iflytek 13, stepfun 12, doubao 11, google 10, baichuan 4, writer 1, xai 1, sarvam 1, cerebras 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.

· Last 72 hours ·

Machine-readable: incidents.json · Licence: CC BY 4.0