AI Latency Tracker

· 45 providers · 4 regions

As of September 25, 2026, the fastest-responding AI inference API by edge latency (time-to-first-byte) is fireworks at 19 ms p50, measured from Asia (Tokyo) (100% uptime, n=289). Rankings differ by region — see the table below.

Independent, provider-neutral latency and uptime of AI inference APIs (OpenAI, Anthropic, Google, Mistral, DeepSeek, xAI, OpenRouter and more), measured directly from multiple regions and updated automatically. How this is measured →

Is any AI API down right now?

2 confirmed outage(s) in the last 24 hours: doubao, Google

45 providers · probed every 5 minutes from 4 regions · last probe Sep 25, 09:13 UTC

None of the 10 providers with a machine-readable status page reports an open incident (checked Sep 25, 08:17 UTC).

all probes succeededsome probes failedhalf or more failedno data

Probe outcomes per provider, hour by hour, last 72 hours (all regions combined)Sep 23Sep 24Sep 25nowSep 22, 10:00 – Sep 22, 19:00 UTC: all 480 probes succeededSep 22, 20:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (http 520)Sep 22, 21:00 – Sep 22, 23:00 UTC: all 144 probes succeededSep 23, 00:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (http 520)Sep 23, 01:00 – Sep 24, 16:00 UTC: all 1922 probes succeededSep 24, 17:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 24, 18:00 – Sep 25, 09:00 UTC: all 735 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 23, 16:00 UTC: all 1490 probes succeededSep 23, 17:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 23, 18:00 – Sep 25, 05:00 UTC: all 1728 probes succeededSep 25, 06:00 UTC: 2 of 51 probes failed — South America (São Paulo) (timeout)Sep 25, 07:00 – Sep 25, 08:00 UTC: all 96 probes succeededSep 25, 09:00 UTC: 1 of 12 probes failed — South America (São Paulo) (timeout)Sep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 22, 18:00 UTC: all 432 probes succeededSep 22, 19:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 22, 20:00 – Sep 22, 22:00 UTC: all 144 probes succeededSep 22, 23:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 23, 00:00 – Sep 23, 11:00 UTC: all 578 probes succeededSep 23, 12:00 UTC: 2 of 48 probes failed — South America (São Paulo) (timeout); US (Central) (timeout)Sep 23, 13:00 – Sep 24, 04:00 UTC: all 768 probes succeededSep 24, 05:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 24, 06:00 – Sep 24, 14:00 UTC: all 432 probes succeededSep 24, 15:00 UTC: 2 of 48 probes failed — Europe (Germany) (timeout); South America (São Paulo) (timeout)Sep 24, 16:00 – Sep 24, 22:00 UTC: all 336 probes succeededSep 24, 23:00 UTC: 4 of 48 probes failed — Europe (Germany) (timeout); South America (São Paulo) (timeout); US (Central) (timeout)Sep 25, 00:00 – Sep 25, 06:00 UTC: all 339 probes succeededSep 25, 07:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 25, 08:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Sep 25, 09:00 UTC: all 12 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 22, 17:00 UTC: all 384 probes succeededSep 22, 18:00 UTC: 1 of 48 probes failed — Europe (Germany) ([Errno 101] Network is unreachable)Sep 22, 19:00 – Sep 25, 09:00 UTC: all 2993 probes succeededSep 22, 10:00 – Sep 25, 09:00 UTC: all 3425 probes succeededSep 22, 10:00 – Sep 22, 14:00 UTC: all 240 probes succeededSep 22, 15:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 22, 16:00 – Sep 22, 22:00 UTC: all 336 probes succeededSep 22, 23:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 23, 00:00 – Sep 23, 02:00 UTC: all 144 probes succeededSep 23, 03:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 23, 04:00 – Sep 23, 11:00 UTC: all 386 probes succeededSep 23, 12:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Sep 23, 13:00 UTC: all 48 probes succeededSep 23, 14:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 23, 15:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 23, 16:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Sep 23, 17:00 – Sep 23, 19:00 UTC: all 144 probes succeededSep 23, 20:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 23, 21:00 – Sep 24, 05:00 UTC: all 432 probes succeededSep 24, 06:00 UTC: 2 of 48 probes failed — Europe (Germany) (timeout); US (Central) (timeout)Sep 24, 07:00 – Sep 24, 08:00 UTC: all 96 probes succeededSep 24, 09:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 24, 10:00 – Sep 24, 12:00 UTC: all 144 probes succeededSep 24, 13:00 UTC: 3 of 48 probes failed — Europe (Germany) (timeout); US (Central) (timeout)Sep 24, 14:00 – Sep 24, 15:00 UTC: all 96 probes succeededSep 24, 16:00 UTC: 1 of 48 probes failed — US (Central) (timeout)Sep 24, 17:00 – Sep 24, 19:00 UTC: all 144 probes succeededSep 24, 20:00 UTC: 2 of 48 probes failed — Europe (Germany) (timeout); US (Central) (timeout)Sep 24, 21:00 – Sep 25, 09:00 UTC: all 591 probes succeeded
openaianthropicgooglemistraldeepseekxaigroqcerebrassambanovatogetherfireworksopenrouterdoubao

Hour by hour for the last 72 hours, all regions combined; hover a cell for the count. Each provider page shows the same view per region. Full incident log →

Which AI API is fastest right now?

RegionFastest AI APIp50 TTFBUptime
Asia (Tokyo)fireworks19 ms100%
Europe (Germany)nscale98 ms100%
South America (São Paulo)openrouter60 ms100%
US (Central)fireworks31 ms100%

Which AI APIs are fastest overall?

Composite score 0–100 (100 = as fast as the region leader), averaged across all 4 measured region(s). How it’s computed →

#ProviderSpeed Index
1fireworks81
2openrouter71
3google59
4meta-llama46
5inference-net42
6baseten42
7cohere37
8sambanova36
9mistral36
10cerebras34
11nscale34
12nebius32
13aleph-alpha32
14replicate32
15reka31

Full ranking — Europe (Germany)

Edge latency (time-to-first-byte), p50/p95, last 24h. Other regions: see the per-region pages below.

#Providerp50 TTFBp95UptimeSamples
1nscale98 ms200 ms100%288
2fireworks98 ms202 ms100%288
3aleph-alpha99 ms293 ms100%288
4google99 ms203 ms100%288
5openrouter99 ms202 ms100%288
6nebius100 ms201 ms100%288
7mistral100 ms205 ms100%288
8inference-net101 ms800 ms100%288
9meta-llama102 ms291 ms100%288
10baichuan191 ms296 ms99.7%288
11baseten198 ms301 ms100%288
12replicate198 ms398 ms100%288
13perplexity199 ms304 ms100%288
14glm199 ms301 ms100%288
15cerebras200 ms389 ms100%288

How fast is each region?

How fast is a specific provider?

Which provider is faster than which?