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

Published 2026-08-01 · 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) Provider Regions hit Which Duration Failed probes Did they say so? 2026-07-31 23:25 friendli 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥14 min 4 No machine-readable status page 2026-07-31 22:47 friendli 2 of 4 Asia (Tokyo), US (Central) ≥3 min 2 No machine-readable status page 2026-07-31 22:09 friendli 3 of 4 Asia (Tokyo), South America (São Paulo), US (Central) ≥13 min 3 No machine-readable status page 2026-07-31 19:19 friendli 3 of 4 Asia (Tokyo), Europe (Germany), US (Central) ≥23 min 5 No machine-readable status page 2026-07-31 10:34 friendli 2 of 4 Europe (Germany), South America (São Paulo) ≥5 min 3 No machine-readable status page 2026-07-30 18:44 sarvam 2 of 4 Europe (Germany), South America (São Paulo) <5 min 2 No machine-readable status page 2026-07-30 06:06 yi-01ai 2 of 4 Asia (Tokyo), US (Central) ≥3 min 2 No machine-readable status page 2026-07-29 18:05 yi-01ai 2 of 4 South America (São Paulo), US (Central) <5 min 2 No machine-readable status page 2026-07-29 15:25 google 2 of 4 Asia (Tokyo), South America (São Paulo) ≥1 min 2 No machine-readable status page 2026-07-29 06:35 yi-01ai 2 of 4 Asia (Tokyo), US (Central) ≥32 min 5 No machine-readable status page 2026-07-29 01:45 google 2 of 4 Europe (Germany), South America (São Paulo) ≥7 min 2 No machine-readable status page 2026-07-28 14:25 google 3 of 4 Asia (Tokyo), South America (São Paulo), US (Central) ≥5 min 3 No machine-readable status page 2026-07-28 03:26 cerebras 2 of 4 Europe (Germany), US (Central) ≥14 min 2 No entry in their status feed 2026-07-27 15:35 nscale 2 of 4 Asia (Tokyo), South America (São Paulo) <5 min 2 No machine-readable status page 2026-07-27 07:25 featherless 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥23 min 16 No machine-readable status page 2026-07-27 02:51 sambanova 2 of 4 Europe (Germany), South America (São Paulo) ≥11 min 3 No entry in their status feed 2026-07-26 18:13 google 2 of 4 Asia (Tokyo), US (Central) <5 min 2 No machine-readable status page 2026-07-26 08:22 doubao 2 of 4 Europe (Germany), South America (São Paulo) ≥13 min 3 No machine-readable status page 2026-07-25 09:20 openai 3 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo) ≥14 min 4 Yes — “Elevated error rates”, 3 min before us 2026-07-31 23:59 friendli 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥25 min 6 No machine-readable status page 2026-07-31 21:27 friendli 3 of 4 Asia (Tokyo), South America (São Paulo), US (Central) ≥22 min 5 No machine-readable status page 2026-07-31 20:14 friendli 3 of 4 Europe (Germany), South America (São Paulo), US (Central) ≥6 min 3 No machine-readable status page 2026-07-31 17:19 friendli 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥20 min 6 No machine-readable status page 2026-07-31 15:52 friendli 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥13 min 5 No machine-readable status page 2026-07-31 15:12 google 2 of 4 Asia (Tokyo), South America (São Paulo) ≥7 min 2 No machine-readable status page 2026-07-31 15:09 friendli 2 of 4 Asia (Tokyo), Europe (Germany) ≥20 min 4 No machine-readable status page 2026-07-31 14:47 google 2 of 4 Asia (Tokyo), South America (São Paulo) ≥7 min 2 No machine-readable status page 2026-07-31 13:40 friendli 3 of 4 Asia (Tokyo), South America (São Paulo), US (Central) ≥40 min 6 No machine-readable status page 2026-07-31 11:29 friendli 3 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo) ≥38 min 6 No machine-readable status page 2026-07-31 11:04 friendli 2 of 4 South America (São Paulo), US (Central) ≥6 min 2 No machine-readable status page 2026-07-30 15:50 google 2 of 4 Asia (Tokyo), US (Central) ≥5 min 2 No machine-readable status page 2026-07-30 15:25 writer 2 of 4 South America (São Paulo), US (Central) <5 min 2 No machine-readable status page 2026-07-29 17:35 yi-01ai 2 of 4 Asia (Tokyo), US (Central) ≥12 min 2 No machine-readable status page 2026-07-29 17:30 doubao 2 of 4 Asia (Tokyo), US (Central) ≥2 min 2 No machine-readable status page 2026-07-29 16:55 google 2 of 4 South America (São Paulo), US (Central) ≥36 min 4 No machine-readable status page 2026-07-29 15:00 google 2 of 4 Asia (Tokyo), South America (São Paulo) ≥1 min 2 No machine-readable status page 2026-07-29 14:00 google 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥37 min 7 No machine-readable status page 2026-07-29 12:41 google 2 of 4 Asia (Tokyo), Europe (Germany) ≥15 min 2 No machine-readable status page 2026-07-29 03:20 stepfun 2 of 4 South America (São Paulo), US (Central) ≥15 min 2 No machine-readable status page 2026-07-28 18:15 cerebras 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥25 min 6 No entry in their status feed 2026-07-28 12:31 google 3 of 4 Asia (Tokyo), Europe (Germany), US (Central) ≥25 min 4 No machine-readable status page 2026-07-27 15:06 deepinfra 2 of 4 Asia (Tokyo), South America (São Paulo) ≥5 min 2 No machine-readable status page 2026-07-27 13:50 stepfun 2 of 4 South America (São Paulo), US (Central) ≥16 min 3 No machine-readable status page 2026-07-27 05:57 yi-01ai 2 of 4 South America (São Paulo), US (Central) ≥10 min 3 No machine-readable status page 2026-07-27 05:40 sensenova 2 of 4 South America (São Paulo), US (Central) ≥2 min 2 No machine-readable status page 2026-07-27 04:03 sambanova 2 of 4 Europe (Germany), South America (São Paulo) ≥41 min 9 No entry in their status feed 2026-07-26 16:46 yi-01ai 2 of 4 Asia (Tokyo), US (Central) ≥5 min 3 No machine-readable status page 2026-07-26 16:46 stepfun 2 of 4 South America (São Paulo), US (Central) ≥5 min 3 No machine-readable status page 2026-07-26 15:26 yi-01ai 2 of 4 Asia (Tokyo), US (Central) ≥5 min 3 No machine-readable status page 2026-07-26 13:25 doubao 2 of 4 Asia (Tokyo), South America (São Paulo) ≥9 min 2 No machine-readable status page 2026-07-26 09:01 iflytek 2 of 4 South America (São Paulo), US (Central) ≥16 min 3 No machine-readable status page 2026-07-25 16:15 stepfun 2 of 4 South America (São Paulo), US (Central) <5 min 2 No machine-readable status page 2026-07-25 16:11 sensenova 2 of 4 Europe (Germany), South America (São Paulo) ≥4 min 2 No machine-readable status page 2026-07-24 11:00 novita 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥6 min 9 No machine-readable status page 2026-07-24 11:00 together 4 of 4 Asia (Tokyo), Europe (Germany), South America (São Paulo), US (Central) ≥6 min 8 No 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 .

Source: https://llmlatency.dev/blog/outages-2026-07 · CC BY 4.0