AI API outages on September 11, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 11, 2026 (UTC) our probes attributed 10 outage(s) to 2 provider(s): Gemini API (Google): 9; SambaNova API: 1. Providers’ own status pages opened 4 entries (OpenAI, Anthropic).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), SambaNova API, OpenAI API, Claude API (Anthropic) · all AI APIs, last 72 hours
Was the Gemini API (Google) down on September 11, 2026?
Yes, measured. 9 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 08:36 UTC, at least 25 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 |
|---|---|---|---|---|---|---|
| 08:36–08:37 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥2 min | 2 | provider outage | timeout |
| 10:15–10:18 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥3 min | 2 | provider outage | http 503; timeout |
| 12:12–12:16 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥3 min | 2 | provider outage | timeout |
| 12:56–12:58 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | ≥3 min | 2 | provider outage | timeout |
| 13:56–14:15 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥20 min | 4 | shared with 3 other provider(s) — not attributed | http 503; timeout |
| 14:33–14:38 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥6 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
| 15:33–15:38 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥6 min | 3 | provider outage | timeout |
| 16:12–16:13 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | provider outage | timeout |
| 16:32–16:36 | requests to gemini-flash-lite-latest | 2 of 4: South America (São Paulo), US (Central) | ≥3 min | 2 | provider outage | http 503; timeout |
| 17:13–17:16 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥3 min | 2 | provider outage | http 503; timeout |
| 17:33–17:36 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥3 min | 2 | provider outage | timeout |
Current Gemini API (Google) status
Was the SambaNova API down on September 11, 2026?
Yes, measured. 1 outage(s) attributed to SambaNova: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 01:48 UTC, at least 5 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 01:48–01:53 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥5 min | 3 | provider outage | timeout |
Was the OpenAI API down on September 11, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI’s own status page opened 3 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- minor Elevated errors for ChatGPT users in Europe · resolved Sep 11, 10:16 UTC
- minor Elevated errors for GPT-5.6 Sol on the API · resolved Sep 11, 11:21 UTC
- minor 1% of ChatGPT Work (mobile/web) turns are failing for existing threads · resolved Sep 12, 01:57 UTC
Was the Claude API (Anthropic) down on September 11, 2026?
Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on Anthropic’s status page, not verified by our probes:
- major Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1 · resolved Sep 11, 14:37 UTC
Current Claude API (Anthropic) status
28 single-region failure(s) were also recorded that day (google 16, iflytek 3, doubao 3, sambanova 2, perplexity 2, baichuan 1, writer 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: Sep 10 · Last 72 hours · Next: Sep 12
Machine-readable: incidents.json · Licence: CC BY 4.0