AI API outages on September 9, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 9, 2026 (UTC) our probes attributed 6 outage(s) to 1 provider(s): Gemini API (Google): 6. Providers’ own status pages opened 2 entries (baseten, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: Gemini API (Google), baseten API, nebius API · all AI APIs, last 72 hours
Was the Gemini API (Google) down on September 9, 2026?
Yes, measured. 6 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 4 of 4 regions at once while no other provider was failing, first at 10:37 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 10:37–10:40 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥2 min | 3 | provider outage | timeout |
| 13:38–13:40 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo) | ≥2 min | 3 | provider outage | timeout |
| 14:38–14:40 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥2 min | 2 | provider outage | timeout |
| 15:18–15:20 | requests to gemini-flash-lite-latest | 3 of 4: Europe (Germany), South America (São Paulo), US (Central) | ≥2 min | 3 | provider outage | timeout |
| 16:00–16:00 | requests to gemini-flash-lite-latest | 2 of 4: Asia (Tokyo), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 16:38–16:40 | requests to gemini-flash-lite-latest | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥2 min | 4 | provider outage | timeout |
Current Gemini API (Google) status
Was the baseten API down on September 9, 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 Nemotron Ultra Model API. **Dedicated Inference is not affected** · resolved Sep 9, 17:49 UTC
Was the nebius API down on September 9, 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:
- minor Unstable compute VM create · resolved Sep 9, 12:41 UTC
28 single-region failure(s) were also recorded that day (google 21, sambanova 2, iflytek 2, hyperbolic 1, openai 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 8 · Last 72 hours · Next: Sep 10
Machine-readable: incidents.json · Licence: CC BY 4.0