AI API outages on October 27, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 27, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): Gemini API (Google): 1; yi-01ai API: 1. Providers’ own status pages opened 4 entries (Anthropic, OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), yi-01ai API, Claude API (Anthropic), OpenAI API, SambaNova API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on October 27, 2026?
Yes, measured. 1 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 16:40 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 15:01–15:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), US (Central) | ≥4 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 16:05–16:05 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 3 other provider(s) — not attributed | timeout |
| 16:40–16:45 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥5 min | 3 | provider outage | timeout |
| 18:05–18:05 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Current Gemini API (Google) status
Was the yi-01ai API down on October 27, 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 10:15 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:15–10:25 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥10 min | 4 | provider outage | timeout |
| 11:10–11:55 | host probes | 2 of 4: Asia (Tokyo), US (Central) | ≥45 min | 6 | shared with 2 other provider(s) — not attributed | timeout |
Was the Claude API (Anthropic) down on October 27, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for Claude Sonnet 5.5 · resolved Oct 27, 09:56 UTC
- major Elevated errors for Claude Sonnet 5.5 · resolved Oct 27, 15:50 UTC
Current Claude API (Anthropic) status
Was the OpenAI API down on October 27, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. OpenAI’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- notice Elevated error rates for most hosted Code Reviews and Security Reviews on private GitHub r · resolved Oct 27, 08:30 UTC
- minor 6.1 Sol Degraded Model Performance · resolved Oct 27, 16:20 UTC
Was the SambaNova API down on October 27, 2026?
Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:00–10:01 | host probes | 2 of 4: Europe (Germany), US (Central) | ≥1 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
64 single-region failure(s) were also recorded that day (yi-01ai 25, google 13, sambanova 3, featherless 3, friendli 3, stepfun 3, ai21 2, hunyuan 2, openai 1, baseten 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.
Previous: Oct 26 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0