AI API outages on October 15, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 15, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): aleph-alpha API: 1. Providers’ own status pages opened 2 entries (OpenAI, nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: aleph-alpha API, OpenAI API, nebius API, yi-01ai API · all AI APIs, last 72 hours
Was the aleph-alpha API down on October 15, 2026?
Yes, measured. 1 outage(s) attributed to aleph-alpha: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 00:40 UTC, at least 5 minutes observed in total. At least once aleph-alpha’s own host answered with an HTTP 5xx.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 00:40–00:45 | host probes | 4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) | ≥5 min | 7 | provider outage | http 500; http 503 |
Is the aleph-alpha API down right now? Live status →
Was the OpenAI API down on October 15, 2026?
Not by our measurements. No failure of OpenAI was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. OpenAI’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on OpenAI’s status page, not verified by our probes:
- major Widespread feature degradation · resolved Oct 15, 18:56 UTC
Is the OpenAI API down right now? Live status →
Was the nebius API down on October 15, 2026?
Not by our measurements. No failure of nebius was seen from two or more regions at once. nebius’s own status page opened 1 entry that day (self-reported, listed below).
Self-reported on nebius’s status page, not verified by our probes:
- major InfiniBand connectivity issues for GPU clusters in eu-west2 · resolved Oct 15, 16:12 UTC
Is the nebius API down right now? Live status →
Was the yi-01ai API down on October 15, 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 |
|---|---|---|---|---|---|---|
| 14:50–15:00 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 2 | shared with 2 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
58 single-region failure(s) were also recorded that day (yi-01ai 18, google 8, iflytek 7, baichuan 6, sensenova 4, stepfun 4, doubao 3, writer 2, openai 1, reka 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.
Machine-readable: incidents.json · Licence: CC BY 4.0