AI API outages on October 10, 2026

UTC day · measured every 5 minutes from 4 regions · method

On October 10, 2026 (UTC) our probes attributed 1 outage(s) to 1 provider(s): stepfun API: 1. Providers’ own status pages opened 1 entry (Groq).

This page is history. Is it down right now?

Live status, updated every 30 minutes: stepfun API, Groq API, SambaNova API, yi-01ai API · all AI APIs, last 72 hours

Was the stepfun API down on October 10, 2026?

Yes, measured. 1 outage(s) attributed to stepfun: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 13:00 UTC, each shorter than one 5-minute probe cycle.

UTCWhat failedRegionsDurationFailed probesVerdictError
13:00–13:01host probes3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo)<5 min3provider outage[Errno 101] Network is unreachable; timeout

Is the stepfun API down right now? Live status →

Was the Groq API down on October 10, 2026?

Not by our measurements. No failure of Groq was seen from two or more regions at once; 1 single-region failure(s) are not called an outage. Groq’s own status page opened 1 entry that day (self-reported, listed below).

Self-reported on Groq’s status page, not verified by our probes:

Is the Groq API down right now? Live status →

Was the SambaNova API down on October 10, 2026?

Not attributably. 1 multi-region failure(s) of SambaNova coincided with failures of other providers, so the cause sat above SambaNova and is not blamed on it. SambaNova’s status page lists nothing that day.

UTCWhat failedRegionsDurationFailed probesVerdictError
18:25–18:26host probes3 of 4: Europe (Germany), South America (São Paulo), US (Central)<5 min3shared with 1 other provider(s) — not attributed[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violatio

Is the SambaNova API down right now? Live status →

Was the yi-01ai API down on October 10, 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.

UTCWhat failedRegionsDurationFailed probesVerdictError
03:50–04:05host probes2 of 4: Asia (Tokyo), US (Central)≥15 min3shared with 2 other provider(s) — not attributedtimeout

Is the yi-01ai API down right now? Live status →

62 single-region failure(s) were also recorded that day (yi-01ai 18, iflytek 6, baichuan 6, doubao 3, stepfun 2, google 2, sensenova 2, friendli 1, targon 1, nscale 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.

· Last 72 hours

Machine-readable: incidents.json · Licence: CC BY 4.0