Question 1

Was the friendli API down on August 5, 2026?

Accepted Answer

Yes, measured. 6 outage(s) attributed to friendli: host probes failed from up to 2 of 4 regions at once while no other provider was failing, first at 01:55 UTC, at least 16 minutes observed in total. At least once friendli’s own host answered with an HTTP 5xx.

Question 2

Was the Gemini API (Google) down on August 5, 2026?

Accepted Answer

Yes, measured. 1 outage(s) attributed to Google: requests to gemini-flash-lite-latest failed from up to 4 of 4 regions at once while no other provider was failing, first at 11:20 UTC, at least 4 minutes observed in total. At least once Google’s own host answered with an HTTP 5xx.

Question 3

Was the OpenAI API down on August 5, 2026?

Accepted Answer

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

Question 4

Was the yi-01ai API down on August 5, 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 06:10 UTC, at least 10 minutes observed in total.

Question 5

Was the Claude API (Anthropic) down on August 5, 2026?

Accepted Answer

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

Question 6

Was the SambaNova API down on August 5, 2026?

Accepted Answer

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.

Question 7

Was the Cohere API down on August 5, 2026?

Accepted Answer

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

Question 8

Was the nebius API down on August 5, 2026?

Accepted Answer

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

Question 9

Was the aleph-alpha API down on August 5, 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 10

Was the iflytek API down on August 5, 2026?

Accepted Answer

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

Question 11

Was the stepfun API down on August 5, 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 12

Was the targon API down on August 5, 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.

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
00:40–00:50	host probes	2 of 4: Asia (Tokyo), US (Central)	≥10 min	2	shared with 1 other provider(s) — not attributed	`http 503`
01:10–01:20	host probes	3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo)	≥10 min	3	shared with 2 other provider(s) — not attributed	`http 503`
01:55–01:55	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	<5 min	2	provider outage	`http 503`
03:05–03:25	host probes	2 of 4: Europe (Germany), US (Central)	≥20 min	4	shared with 3 other provider(s) — not attributed	`http 503`
05:40–05:50	host probes	2 of 4: South America (São Paulo), US (Central)	≥10 min	3	provider outage	`http 503`
06:35–06:35	host probes	2 of 4: South America (São Paulo), US (Central)	<5 min	2	provider outage	`http 503`
07:10–07:20	host probes	2 of 4: Europe (Germany), South America (São Paulo)	≥10 min	2	shared with 1 other provider(s) — not attributed	`http 503`
07:40–07:40	host probes	2 of 4: Europe (Germany), US (Central)	<5 min	2	provider outage	`http 503`
10:00–10:35	host probes	3 of 4: Europe (Germany), South America (São Paulo), US (Central)	≥35 min	7	shared with 3 other provider(s) — not attributed	`http 503`
11:15–11:15	host probes	2 of 4: Europe (Germany), South America (São Paulo)	<5 min	2	provider outage	`http 503`
12:35–12:40	host probes	2 of 4: Europe (Germany), US (Central)	≥5 min	3	shared with 2 other provider(s) — not attributed	`http 503`
13:15–13:20	host probes	2 of 4: Europe (Germany), US (Central)	≥5 min	2	shared with 1 other provider(s) — not attributed	`http 503`
14:25–14:35	host probes	2 of 4: South America (São Paulo), US (Central)	≥10 min	2	shared with 1 other provider(s) — not attributed	`http 503`
16:50–17:05	host probes	2 of 4: South America (São Paulo), US (Central)	≥15 min	3	shared with 2 other provider(s) — not attributed	`http 503`
17:30–17:35	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥5 min	2	shared with 2 other provider(s) — not attributed	`http 503`
17:50–18:10	host probes	2 of 4: Asia (Tokyo), South America (São Paulo)	≥20 min	3	shared with 1 other provider(s) — not attributed	`http 503`
18:30–18:55	host probes	3 of 4: Asia (Tokyo), South America (São Paulo), US (Central)	≥25 min	4	shared with 1 other provider(s) — not attributed	`http 503`
19:15–19:15	host probes	2 of 4: Europe (Germany), US (Central)	<5 min	2	shared with 3 other provider(s) — not attributed	`http 503`
19:40–19:45	host probes	2 of 4: South America (São Paulo), US (Central)	≥5 min	2	shared with 1 other provider(s) — not attributed	`http 503`
20:40–20:45	host probes	2 of 4: South America (São Paulo), US (Central)	≥5 min	3	provider outage	`http 503`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
11:20–11:25	requests to gemini-flash-lite-latest	4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)	≥4 min	4	provider outage	`http 503`
12:10–12:15	requests to gemini-flash-lite-latest	4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)	≥5 min	4	shared with 2 other provider(s) — not attributed	`The read operation timed out; http 503`
13:50–13:55	requests to gemini-flash-lite-latest	4 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)	≥5 min	4	shared with 2 other provider(s) — not attributed	`The read operation timed out`
14:15–14:20	requests to gemini-flash-lite-latest	3 of 4: Asia (Tokyo), Europe (Germany), South America (São Paulo)	≥5 min	3	shared with 1 other provider(s) — not attributed	`The read operation timed out`

UTC	What failed	Regions	Duration	Failed probes	Verdict	Error
23:00–23:20	host probes	2 of 4: Europe (Germany), US (Central)	≥20 min	3	provider outage	`timeout`
23:50–00:00	host probes	2 of 4: Asia (Tokyo), US (Central)	≥10 min	3	shared with 1 other provider(s) — not attributed	`timeout`

AI API outages on August 5, 2026