Question 1

Was the SambaNova API down on October 2, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to SambaNova: host probes failed from up to 3 of 4 regions at once while no other provider was failing, first at 19:52 UTC, at least 30 minutes observed in total. SambaNova’s status page lists nothing that day.

Question 2

Was the doubao API down on October 2, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to doubao: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 21:18 UTC, at least 11 minutes observed in total.

Question 3

Was the sensenova API down on October 2, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to sensenova: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 22:30 UTC, at least 2 minutes observed in total.

Question 4

Was the OpenAI API down on October 2, 2026?

Accepted Answer

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

Question 5

Was the Gemini API (Google) down on October 2, 2026?

Accepted Answer

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

Question 6

Was the xAI API down on October 2, 2026?

Accepted Answer

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

Question 7

Was the nebius API down on October 2, 2026?

Accepted Answer

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

Question 8

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

Accepted Answer

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.

Question 9

Was the baichuan API down on October 2, 2026?

Accepted Answer

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

Question 10

Was the deepinfra API down on October 2, 2026?

Accepted Answer

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

Question 11

Was the friendli API down on October 2, 2026?

Accepted Answer

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

Question 12

Was the glm API down on October 2, 2026?

Accepted Answer

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

Question 13

Was the minimax API down on October 2, 2026?

Accepted Answer

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

Question 14

Was the nscale API down on October 2, 2026?

Accepted Answer

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

Question 15

Was the stepfun API down on October 2, 2026?

Accepted Answer

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.

Question 16

Was the targon API down on October 2, 2026?

Accepted Answer

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

Question 17

Was the yi-01ai API down on October 2, 2026?

Accepted Answer

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
03:23–06:28	host probes	2 of 4: Asia (Tokyo), US (Central)	≥185 min	33	shared with 39 other provider(s) — not attributed	`[Errno -5] No address associated with hostname`
06:43–08:43	host probes	2 of 4: Asia (Tokyo), US (Central)	≥120 min	21	shared with 37 other provider(s) — not attributed	`[Errno -5] No address associated with hostname`
19:52–20:22	host probes	3 of 4: Europe (Germany), South America (São Paulo), US (Central)	≥30 min	17	provider outage	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
03:23–03:46	host probes	3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)	≥23 min	6	shared with 25 other provider(s) — not attributed	`[Errno -5] No address associated with hostname; timeout`
04:13–05:08	host probes	2 of 4: Asia (Tokyo), US (Central)	≥55 min	9	shared with 24 other provider(s) — not attributed	`[Errno -5] No address associated with hostname`
21:18–21:30	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥11 min	2	provider outage	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
03:51–04:02	host probes	2 of 4: Europe (Germany), US (Central)	≥10 min	2	shared with 21 other provider(s) — not attributed	`[Errno -2] Name or service not known; timeout`
22:30–22:32	host probes	4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)	≥2 min	4	provider outage	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
04:57–05:17	requests to gemini-flash-lite-latest	2 of 4: Europe (Germany), US (Central)	≥20 min	3	shared with 14 other provider(s) — not attributed	`timeout`
17:38–17:51	requests to gemini-flash-lite-latest	2 of 4: Asia (Tokyo), US (Central)	≥13 min	2	shared with 11 other provider(s) — not attributed	`http 503; timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
03:51–04:03	host probes	2 of 4: Asia (Tokyo), US (Central)	≥12 min	2	shared with 25 other provider(s) — not attributed	`[Errno 101] Network is unreachable`
07:56–08:03	host probes	2 of 4: Asia (Tokyo), US (Central)	≥7 min	2	shared with 18 other provider(s) — not attributed	`[Errno 101] Network is unreachable`

AI API outages on October 2, 2026