# AI API outages on October 30, 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 October 30, 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 14:35 UTC: Elevated errors for GPT Image 2 API image edits (minor)
- self-reported 19:38 UTC: Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experience (minor)

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

## Was the TypeSafe API down on October 30, 2026?

Not by our measurements. No failure of TypeSafe was seen from two or more regions at once. TypeSafe's own status page opened 1 entry that day (self-reported, listed below).
- self-reported 20:00 UTC: System overload (none)

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

## Was the aleph-alpha API down on October 30, 2026?

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

| UTC | What failed | Regions | Duration (lower bound) | Failed probes | Verdict |
| --- | --- | --- | --- | --- | --- |
| 08:27-08:30 | host probes | ap-tokyo eu-hetzner sa-east us-central | >=3 min | 4 | unattributed |

Live status now: https://llmlatency.dev/provider/aleph-alpha

Source: https://llmlatency.dev/incidents/2026-10-30 · CC BY 4.0