AI API outages in July 2026: who went down, and who admitted it

· covers July 2026

In July 2026 we attributed 19 outage(s) to a provider, could not attribute 36 more, and recorded 336 isolated single-region failures.

Which AI APIs went down, and did they say so?

Started (UTC)ProviderRegions hitWhichDurationFailed probesDid they say so?
2026-07-31 23:25friendli4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥14 min4No machine-readable status page
2026-07-31 22:47friendli2 of 4Asia (Tokyo), US (Central)≥3 min2No machine-readable status page
2026-07-31 22:09friendli3 of 4Asia (Tokyo), South America (São Paulo), US (Central)≥13 min3No machine-readable status page
2026-07-31 19:19friendli3 of 4Asia (Tokyo), Europe (Germany), US (Central)≥23 min5No machine-readable status page
2026-07-31 10:34friendli2 of 4Europe (Germany), South America (São Paulo)≥5 min3No machine-readable status page
2026-07-30 18:44sarvam2 of 4Europe (Germany), South America (São Paulo)<5 min2No machine-readable status page
2026-07-30 06:06yi-01ai2 of 4Asia (Tokyo), US (Central)≥3 min2No machine-readable status page
2026-07-29 18:05yi-01ai2 of 4South America (São Paulo), US (Central)<5 min2No machine-readable status page
2026-07-29 15:25google2 of 4Asia (Tokyo), South America (São Paulo)≥1 min2No machine-readable status page
2026-07-29 06:35yi-01ai2 of 4Asia (Tokyo), US (Central)≥32 min5No machine-readable status page
2026-07-29 01:45google2 of 4Europe (Germany), South America (São Paulo)≥7 min2No machine-readable status page
2026-07-28 14:25google3 of 4Asia (Tokyo), South America (São Paulo), US (Central)≥5 min3No machine-readable status page
2026-07-28 03:26cerebras2 of 4Europe (Germany), US (Central)≥14 min2No entry in their status feed
2026-07-27 15:35nscale2 of 4Asia (Tokyo), South America (São Paulo)<5 min2No machine-readable status page
2026-07-27 07:25featherless4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥23 min16No machine-readable status page
2026-07-27 02:51sambanova2 of 4Europe (Germany), South America (São Paulo)≥11 min3No entry in their status feed
2026-07-26 18:13google2 of 4Asia (Tokyo), US (Central)<5 min2No machine-readable status page
2026-07-26 08:22doubao2 of 4Europe (Germany), South America (São Paulo)≥13 min3No machine-readable status page
2026-07-25 09:20openai3 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo)≥14 min4Yes — “Elevated error rates”, 3 min before us
2026-07-31 23:59friendli4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥25 min6No machine-readable status page
2026-07-31 21:27friendli3 of 4Asia (Tokyo), South America (São Paulo), US (Central)≥22 min5No machine-readable status page
2026-07-31 20:14friendli3 of 4Europe (Germany), South America (São Paulo), US (Central)≥6 min3No machine-readable status page
2026-07-31 17:19friendli4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥20 min6No machine-readable status page
2026-07-31 15:52friendli4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥13 min5No machine-readable status page
2026-07-31 15:12google2 of 4Asia (Tokyo), South America (São Paulo)≥7 min2No machine-readable status page
2026-07-31 15:09friendli2 of 4Asia (Tokyo), Europe (Germany)≥20 min4No machine-readable status page
2026-07-31 14:47google2 of 4Asia (Tokyo), South America (São Paulo)≥7 min2No machine-readable status page
2026-07-31 13:40friendli3 of 4Asia (Tokyo), South America (São Paulo), US (Central)≥40 min6No machine-readable status page
2026-07-31 11:29friendli3 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo)≥38 min6No machine-readable status page
2026-07-31 11:04friendli2 of 4South America (São Paulo), US (Central)≥6 min2No machine-readable status page
2026-07-30 15:50google2 of 4Asia (Tokyo), US (Central)≥5 min2No machine-readable status page
2026-07-30 15:25writer2 of 4South America (São Paulo), US (Central)<5 min2No machine-readable status page
2026-07-29 17:35yi-01ai2 of 4Asia (Tokyo), US (Central)≥12 min2No machine-readable status page
2026-07-29 17:30doubao2 of 4Asia (Tokyo), US (Central)≥2 min2No machine-readable status page
2026-07-29 16:55google2 of 4South America (São Paulo), US (Central)≥36 min4No machine-readable status page
2026-07-29 15:00google2 of 4Asia (Tokyo), South America (São Paulo)≥1 min2No machine-readable status page
2026-07-29 14:00google4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥37 min7No machine-readable status page
2026-07-29 12:41google2 of 4Asia (Tokyo), Europe (Germany)≥15 min2No machine-readable status page
2026-07-29 03:20stepfun2 of 4South America (São Paulo), US (Central)≥15 min2No machine-readable status page
2026-07-28 18:15cerebras4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥25 min6No entry in their status feed
2026-07-28 12:31google3 of 4Asia (Tokyo), Europe (Germany), US (Central)≥25 min4No machine-readable status page
2026-07-27 15:06deepinfra2 of 4Asia (Tokyo), South America (São Paulo)≥5 min2No machine-readable status page
2026-07-27 13:50stepfun2 of 4South America (São Paulo), US (Central)≥16 min3No machine-readable status page
2026-07-27 05:57yi-01ai2 of 4South America (São Paulo), US (Central)≥10 min3No machine-readable status page
2026-07-27 05:40sensenova2 of 4South America (São Paulo), US (Central)≥2 min2No machine-readable status page
2026-07-27 04:03sambanova2 of 4Europe (Germany), South America (São Paulo)≥41 min9No entry in their status feed
2026-07-26 16:46yi-01ai2 of 4Asia (Tokyo), US (Central)≥5 min3No machine-readable status page
2026-07-26 16:46stepfun2 of 4South America (São Paulo), US (Central)≥5 min3No machine-readable status page
2026-07-26 15:26yi-01ai2 of 4Asia (Tokyo), US (Central)≥5 min3No machine-readable status page
2026-07-26 13:25doubao2 of 4Asia (Tokyo), South America (São Paulo)≥9 min2No machine-readable status page
2026-07-26 09:01iflytek2 of 4South America (São Paulo), US (Central)≥16 min3No machine-readable status page
2026-07-25 16:15stepfun2 of 4South America (São Paulo), US (Central)<5 min2No machine-readable status page
2026-07-25 16:11sensenova2 of 4Europe (Germany), South America (São Paulo)≥4 min2No machine-readable status page
2026-07-24 11:00novita4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥6 min9No machine-readable status page
2026-07-24 11:00together4 of 4Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central)≥6 min8No machine-readable status page

How is this decided?

An outage is attributed to a provider only when it failed from two or more regions at once and no other provider was failing in the same minutes. A failure shared with other providers has a cause above all of them. Full method: the incident log.

Other measurements from the same period

This post is a snapshot. The live figures behind it: /incidents · all posts