AI API outages on September 17, 2026
UTC day · measured every 5 minutes from 4 regions · method
On September 17, 2026 (UTC) our probes attributed 2 outage(s) to 1 provider(s): SambaNova API: 2. Providers’ own status pages opened 4 entries (OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: SambaNova API, OpenAI API, Gemini API (Google), nebius API, yi-01ai API · all AI APIs, last 72 hours
Was the SambaNova API down on September 17, 2026?
Yes, measured. 2 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 00:15 UTC, at least 20 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:15–00:15 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | <5 min | 2 | provider outage | timeout |
| 08:32–08:52 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥20 min | 8 | provider outage | timeout |
Is the SambaNova API down right now? Live status →
Was the OpenAI API down on September 17, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once. 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:
- major Elevated errors affecting ChatGPT Work mode · resolved Sep 17, 20:24 UTC
- minor We are seeing elevated error rates across API models · resolved Sep 17, 21:50 UTC
Is the OpenAI API down right now? Live status →
Was the Gemini API (Google) down on September 17, 2026?
Not attributably. 1 multi-region failure(s) of Google coincided with failures of other providers, so the cause sat above Google and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 06:05–06:05 | requests to gemini-flash-lite-latest | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | <5 min | 3 | shared with 2 other provider(s) — not attributed | timeout |
Is the Gemini API (Google) down right now? Live status →
Was the nebius API down on September 17, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius’s own status page opened 2 entries that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- notice Resuming IAM accounts is unavailable · resolved Sep 17, 11:45 UTC
- major Compute services are partially unavailable for customers · resolved Sep 17, 17:09 UTC
Is the nebius API down right now? Live status →
Was the yi-01ai API down on September 17, 2026?
Not attributably. 1 multi-region failure(s) of yi-01ai coincided with failures of other providers, so the cause sat above yi-01ai and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 09:05–09:25 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥20 min | 3 | shared with 1 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
43 single-region failure(s) were also recorded that day (google 20, yi-01ai 13, sambanova 4, openrouter 2, writer 1, targon 1, doubao 1, minimax 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.
← Sep 16 · Last 72 hours · Sep 18 →
Machine-readable: incidents.json · Licence: CC BY 4.0