Question 1

Was the doubao API down on September 29, 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 20:30 UTC, each shorter than one 5-minute probe cycle.

Question 2

Was the iflytek API down on September 29, 2026?

Accepted Answer

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

Question 3

Was the inference-net API down on September 29, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to inference-net: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 22:00 UTC, at least 11 minutes observed in total. At least once inference-net’s own host answered with an HTTP 5xx.

Question 4

Was the kimi API down on September 29, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to kimi: host probes failed from up to 4 of 4 regions at once while no other provider was failing, first at 23:20 UTC, at least 36 minutes observed in total. At least once kimi’s own host answered with an HTTP 5xx.

Question 5

Was the yi-01ai API down on September 29, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to yi-01ai: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 10:00 UTC, at least 5 minutes observed in total.

Question 6

Was the OpenAI API down on September 29, 2026?

Accepted Answer

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 2 entries that day (self-reported, listed below).

Question 7

Was the Claude API (Anthropic) down on September 29, 2026?

Accepted Answer

Not by our measurements. No failure of Anthropic was seen from two or more regions at once. Anthropic’s own status page opened 1 entry that day (self-reported, listed below).

Question 8

Was the TypeSafe API down on September 29, 2026?

Accepted Answer

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

Question 9

Was the Gemini API (Google) down on September 29, 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 10

Was the baseten API down on September 29, 2026?

Accepted Answer

Not by our measurements. No failure of baseten was seen from two or more regions at once. baseten’s own status page opened 2 entries that day (self-reported, listed below).

Question 11

Was the baichuan API down on September 29, 2026?

Accepted Answer

Not attributably. 6 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 12

Was the sarvam API down on September 29, 2026?

Accepted Answer

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

Question 13

Was the sensenova API down on September 29, 2026?

Accepted Answer

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

Question 14

Was the stepfun API down on September 29, 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.

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
03:55–04:05	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥10 min	3	shared with 1 other provider(s) — not attributed	`timeout`
08:30–08:35	host probes	3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo)	≥5 min	4	shared with 1 other provider(s) — not attributed	`timeout`
20:30–20:31	host probes	2 of 4: Europe (Germany), South America (São Paulo)	<5 min	2	provider outage	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
08:50–09:05	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥15 min	3	shared with 5 other provider(s) — not attributed	`timeout`
09:30–09:55	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥25 min	4	shared with 7 other provider(s) — not attributed	`timeout`
13:15–13:21	host probes	2 of 4: Asia (Tokyo), Europe (Germany)	≥6 min	2	provider outage	`timeout`
14:55–15:10	host probes	3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)	≥15 min	3	shared with 4 other provider(s) — not attributed	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
06:00–06:00	host probes	2 of 4: South America (São Paulo), US (Central)	<5 min	2	shared with 2 other provider(s) — not attributed	`timeout`
08:40–09:05	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥25 min	4	shared with 5 other provider(s) — not attributed	`timeout`
10:00–10:05	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥5 min	2	provider outage	`timeout`
10:55–11:05	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥10 min	3	shared with 6 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
14:50–15:15	host probes	2 of 4: Asia (Tokyo), US (Central)	≥25 min	3	shared with 4 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
16:05–16:15	host probes	2 of 4: Asia (Tokyo), US (Central)	≥10 min	2	shared with 1 other provider(s) — not attributed	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
12:35–12:45	requests to gemini-flash-lite-latest	4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)	≥9 min	4	shared with 1 other provider(s) — not attributed	`timeout`
14:16–14:25	requests to gemini-flash-lite-latest	2 of 4: Europe (Germany), US (Central)	≥9 min	2	shared with 2 other provider(s) — not attributed	`timeout`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
05:55–05:56	host probes	2 of 4: Asia (Tokyo), Europe (Germany)	<5 min	2	shared with 3 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
07:20–07:45	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥25 min	3	shared with 3 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
08:50–08:55	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥5 min	2	shared with 5 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
12:45–12:50	host probes	2 of 4: Asia (Tokyo), US (Central)	≥5 min	2	shared with 1 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
14:00–14:10	host probes	3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)	≥10 min	3	shared with 6 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`
15:25–15:55	host probes	3 of 4: Asia (Tokyo), Europe (Germany), US (Central)	≥30 min	6	shared with 2 other provider(s) — not attributed	`[Errno 101] Network is unreachable; timeout`

AI API outages on September 29, 2026