# AI API outages on September 17, 2026 (UTC)

Measured every 5 minutes from 4 regions. An outage is attributed to a provider only when it failed from 2+ regions at once and no other provider failed in the same minutes.

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 00:15-00:15 | host probes | eu-hetzner sa-east | <5 min | 2 | provider_outage |
| 08:32-08:52 | host probes | eu-hetzner sa-east | >=20 min | 8 | provider_outage |

Live status now: https://llmlatency.dev/provider/sambanova

## 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 19:03 UTC: Elevated errors affecting ChatGPT Work mode (major)
- self-reported 21:29 UTC: We are seeing elevated error rates across API models (minor)

Live status now: https://llmlatency.dev/provider/openai

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 06:05-06:05 | requests to gemini-flash-lite-latest | ap-tokyo sa-east us-central | <5 min | 3 | unattributed |

Live status now: https://llmlatency.dev/provider/google

## 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 10:46 UTC: Resuming IAM accounts is unavailable (none)
- self-reported 16:26 UTC: Compute services are partially unavailable for customers (major)

Live status now: https://llmlatency.dev/provider/nebius

## 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 (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 09:05-09:25 | host probes | ap-tokyo eu-hetzner | >=20 min | 3 | unattributed |

Live status now: https://llmlatency.dev/provider/yi-01ai

Source: https://llmlatency.dev/incidents/2026-09-17 · CC BY 4.0