AI API outages on September 13, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 13, 2026 (UTC) our probes attributed 3 outage(s) to 3 provider(s): Gemini API (Google): 1; SambaNova API: 1; featherless API: 1. Providers’ own status pages opened 2 entries (OpenAI).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), SambaNova API, featherless API, OpenAI API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on September 13, 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 17:00 UTC, at least 5 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 17:00–17:05 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥5 min | 3 | provider outage | timeout |
Current Gemini API (Google) status
Was the SambaNova API down on September 13, 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 13:33 UTC, at least 7 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:33–13:41 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥7 min | 2 | provider outage | timeout |
Was the featherless API down on September 13, 2026?
Yes, measured. 1 outage(s) attributed to featherless: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 15:20 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:35–14:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥10 min | 11 | shared with 1 other provider(s) — not attributed | http 503; timeout |
| 15:20–15:20 | host probes | 2 of 4: Europe (Germany), US (Central) | <5 min | 2 | provider outage | timeout |
Current featherless API status
Was the OpenAI API down on September 13, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 3 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:
- minor Codex GitHub Review and Pull Request Failures · resolved Sep 13, 09:53 UTC
- minor Elevated errors for ChatGPT users in Europe · resolved Sep 13, 17:47 UTC
21 single-region failure(s) were also recorded that day (google 10, openai 3, featherless 2, sambanova 2, cerebras 1, friendli 1, hunyuan 1, doubao 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 12 · Last 72 hours · Next: Sep 14
Machine-readable: incidents.json · Licence: CC BY 4.0