AI API outages on September 14, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 14, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): Gemini API (Google): 1. Providers’ own status pages opened 5 entries (OpenAI, baseten, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), OpenAI API, baseten API, nebius API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on September 14, 2026?
Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 2 of 4 regions at once while no other provider was failing, first at 13:20 UTC, each shorter than one 5-minute probe cycle.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 13:20–13:20 | requests to gemini-flash-lite-latest | 2 of 4: Europe (Germany), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
Current Gemini API (Google) status
Was the OpenAI API down on September 14, 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 3 entries that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- notice Elevated error rates for Codex and ChatGPT Work · resolved Sep 14, 03:57 UTC
- minor Elevated errors affecting Work Mode in ChatGPT · resolved Sep 15, 03:11 UTC
- notice Degraded Performance affecting Agents API · resolved Sep 14, 23:39 UTC
Was the baseten API down on September 14, 2026?
Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on baseten’s status page, not verified by our probes:
- minor Partial outage on Kimi K3 model API inference (non-US only) · resolved Sep 14, 17:03 UTC
Was the nebius API down on September 14, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. 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 Managed Service for SkyPilot: cluster creation and update requests failing in eu-north1 · resolved Sep 15, 15:33 UTC
24 single-region failure(s) were also recorded that day (google 7, sambanova 4, hunyuan 2, minimax 2, baichuan 2, openai 1, deepseek 1, upstage 1, qwen 1, nebius 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 13 · Last 72 hours · Next: Sep 15
Machine-readable: incidents.json · Licence: CC BY 4.0