AI Latency Tracker

· 45 providers · 4 regions

As of September 06, 2026, the fastest-responding AI inference API by edge latency (time-to-first-byte) is fireworks at 20 ms p50, measured from Asia (Tokyo) (100% uptime, n=288). 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?

1 confirmed outage(s) in the last 24 hours: yi-01ai

45 providers · probed every 5 minutes from 4 regions · last probe Sep 6, 17:10 UTC

None of the 10 providers with a machine-readable status page reports an open incident (checked Sep 6, 16: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 4Sep 5Sep 6nowSep 3, 18:00 – Sep 6, 03:00 UTC: all 2784 probes succeededSep 6, 04:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (http 520)Sep 6, 05:00 – Sep 6, 17:00 UTC: all 589 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 4, 23:00 UTC: all 1440 probes succeededSep 5, 00:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 5, 01:00 UTC: all 48 probes succeededSep 5, 02:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 5, 03:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 5, 04:00 UTC: 1 of 48 probes failed — South America (São Paulo) (timeout)Sep 5, 05:00 – Sep 5, 09:00 UTC: all 240 probes succeededSep 5, 10:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 5, 11:00 – Sep 6, 02:00 UTC: all 768 probes succeededSep 6, 03:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 6, 04:00 – Sep 6, 15:00 UTC: all 576 probes succeededSep 6, 16:00 UTC: 1 of 48 probes failed — Europe (Germany) (timeout)Sep 6, 17:00 UTC: all 13 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 6, 17:00 UTC: all 3421 probes succeededSep 3, 18:00 – Sep 4, 01:00 UTC: all 384 probes succeededSep 4, 02:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 03:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 04:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 05:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 06:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 07:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 08:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 09:00 UTC: 5 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 10:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 11:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 12:00 UTC: all 48 probes succeededSep 4, 13:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 14:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 15:00 UTC: 4 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 16:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 17:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 18:00 UTC: all 48 probes succeededSep 4, 19:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 4, 20:00 – Sep 5, 00:00 UTC: all 240 probes succeededSep 5, 01:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 02:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 03:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 04:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 05:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 06:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 07:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 08:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 09:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 10:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 11:00 UTC: all 48 probes succeededSep 5, 12:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 13:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 14:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 15:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 16:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 5, 17:00 – Sep 6, 00:00 UTC: all 384 probes succeededSep 6, 01:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 02:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 03:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 04:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 05:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 06:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 07:00 – Sep 6, 08:00 UTC: all 96 probes succeededSep 6, 09:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 10:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 11:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 12:00 UTC: 3 of 48 probes failed — Asia (Tokyo) (timeout); South America (São Paulo) (timeout)Sep 6, 13:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 14:00 UTC: 1 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 15:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 16:00 UTC: 2 of 48 probes failed — Asia (Tokyo) (timeout)Sep 6, 17:00 UTC: all 13 probes succeeded
openaianthropicgooglemistraldeepseekxaigroqcerebrassambanovatogetherfireworksopenrouteryi-01ai

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)fireworks20 ms100%
Europe (Germany)fireworks98 ms100%
South America (São Paulo)openrouter56 ms100%
US (Central)google40 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
1openrouter79
2fireworks77
3google66
4meta-llama49
5sambanova41
6baseten40
7mistral37
8cerebras37
9cohere37
10inference-net37
11nscale34
12replicate34
13reka34
14perplexity33
15anthropic33

Full ranking — Europe (Germany)

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

#Providerp50 TTFBp95UptimeSamples
1fireworks98 ms200 ms100%288
2nscale99 ms202 ms100%288
3openrouter99 ms201 ms100%288
4aleph-alpha99 ms201 ms100%288
5google99 ms204 ms100%288
6nebius100 ms205 ms100%288
7mistral100 ms296 ms100%288
8meta-llama101 ms299 ms100%288
9inference-net107 ms801 ms100%288
10baichuan181 ms605 ms100%288
11baseten198 ms300 ms100%288
12cerebras199 ms382 ms100%288
13glm199 ms302 ms100%288
14perplexity199 ms396 ms100%288
15anthropic200 ms302 ms100%288

How fast is each region?

How fast is a specific provider?

Which provider is faster than which?