AI API outages on October 3, 2026
UTC day · measured every 5 minutes from 4 regions · method
On October 3, 2026 (UTC) our probes attributed 2 outage(s) to 2 provider(s): SambaNova API: 1; doubao API: 1. Providers’ own status pages opened 1 entry (nebius).
This page is history. Is it down right now?
Live status, updated every 30 minutes: SambaNova API, doubao API, nebius API, stepfun API, yi-01ai API · all AI APIs, last 72 hours
Was the SambaNova API down on October 3, 2026?
Yes, measured. 1 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 09:07 UTC, at least 8 minutes observed in total. SambaNova’s status page lists nothing that day.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 09:07–09:15 | host probes | 2 of 4: Europe (Germany), South America (São Paulo) | ≥8 min | 2 | provider outage | timeout |
Is the SambaNova API down right now? Live status →
Was the doubao API down on October 3, 2026?
Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 14:35 UTC, at least 10 minutes observed in total.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 14:35–14:45 | host probes | 3 of 4: Asia (Tokyo), South America (São Paulo), US (Central) | ≥10 min | 5 | provider outage | timeout |
| 21:57–22:10 | host probes | 2 of 4: Asia (Tokyo), Europe (Germany) | ≥12 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the doubao API down right now? Live status →
Was the nebius API down on October 3, 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:
- minor InfiniBand connectivity issues for GPU clusters in eu-west2 · resolved Oct 3, 08:59 UTC
Is the nebius API down right now? Live status →
Was the stepfun API down on October 3, 2026?
Not attributably. 1 multi-region failure(s) of stepfun coincided with failures of other providers, so the cause sat above stepfun and is not blamed on it.
| UTC | What failed | Regions | Duration | Failed probes | Verdict | Error |
|---|---|---|---|---|---|---|
| 22:10–22:10 | host probes | 2 of 4: Asia (Tokyo), US (Central) | <5 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the stepfun API down right now? Live status →
Was the yi-01ai API down on October 3, 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 |
|---|---|---|---|---|---|---|
| 10:40–10:50 | host probes | 2 of 4: Asia (Tokyo), South America (São Paulo) | ≥10 min | 2 | shared with 1 other provider(s) — not attributed | timeout |
Is the yi-01ai API down right now? Live status →
34 single-region failure(s) were also recorded that day (yi-01ai 13, doubao 6, iflytek 3, baseten 3, google 3, sensenova 2, stepfun 2, xai 1, cohere 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