# AI API outages on September 18, 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 OpenAI API down on September 18, 2026?

Not by our measurements. No failure of OpenAI was seen from two or more regions at once. OpenAI's own status page opened 3 entries that day (self-reported, listed below).
- self-reported 21:36 UTC: Delayed support responses (none)
- self-reported 22:29 UTC: Overbilling for OpenAI-hosted containers in the Agent API (none)
- self-reported 23:00 UTC: SSO sign-in and SCIM provisioning issues (none)

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

## Was the Gemini API (Google) down on September 18, 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 |
| --- | --- | --- | --- | --- | --- |
| 12:58-13:05 | requests to gemini-flash-lite-latest | eu-hetzner sa-east | >=7 min | 2 | unattributed |

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

## Was the iflytek API down on September 18, 2026?

Not attributably. 1 multi-region failure(s) of iflytek coincided with failures of other providers, so the cause sat above iflytek and is not blamed on it.

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 15:20-15:25 | host probes | ap-tokyo us-central | >=5 min | 2 | unattributed |

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

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