AI API outages on October 30, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 30, 2026 (UTC) no AI API outage could be attributed to a provider: nothing failed from two or more regions at once without other providers failing alongside. Providers’ own status pages opened 3 entries (OpenAI, TypeSafe).
This page is history. Is it down right now?
Live status, updated every 30 minutes: OpenAI API, TypeSafe API, aleph-alpha API · all AI APIs, last 72 hours
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 on OpenAI’s status page, not verified by our probes:
- minor Elevated errors for GPT Image 2 API image edits · resolved Oct 30, 18:36 UTC
- minor Elevated errors with search in Dots, ChatGPT Work, and certain ChatGPT thinking experience · resolved Oct 30, 21:14 UTC
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 on TypeSafe’s status page, not verified by our probes:
- notice System overload · resolved Oct 30, 21:15 UTC
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 | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 08:27–08:30 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥3 min | 4 | shared with 1 other provider(s) — not attributed | http 503 |
Current aleph-alpha API status
55 single-region failure(s) were also recorded that day (yi-01ai 34, sambanova 7, doubao 4, google 4, aleph-alpha 2, iflytek 1, reka 1, ai21 1, featherless 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: Oct 29 · Last 72 hours
Machine-readable: incidents.json · Licence: CC BY 4.0