HomeAp tokyo
Data API

Fastest AI API from Asia (Tokyo)

· edge + inference latency

As of October 22, 2026, measured from Asia (Tokyo), the fastest AI inference API by edge latency (time-to-first-byte) is fireworks at 17 ms p50 (n=289).

Which AI API is fastest from Asia (Tokyo)?

Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics
Endpoint response (TTFB)Network connection and the first response byte, without model inference.
Typical · p5050% of successful timed samples finish within this time.
Slower · p9595% of successful timed samples finish within this time.
#ProviderTypical (p50 TTFB)Slower (p95)UptimeSamples
1fireworks17 ms57 ms100%289
2sambanova26 ms79 ms100%289
3upstage60 ms76 ms100%289
4openrouter62 ms126 ms100%289
5google66 ms120 ms100%289
6glm91 ms153 ms100%289
7meta-llama115 ms282 ms100%289
8kimi128 ms210 ms100%289
9ernie136 ms166 ms100%289
10baichuan141 ms538 ms99.3%289
11typesafe146 ms162 ms100%289
12novita152 ms214 ms100%289
13qwen158 ms219 ms100%289
14groq166 ms243 ms100%289
15baseten167 ms195 ms100%289
16xai172 ms264 ms100%289
17cohere181 ms223 ms100%289
18deepseek182 ms252 ms100%289
19together184 ms381 ms100%289
20yi-01ai192 ms1105 ms88.2%289
21replicate193 ms476 ms100%289
22cerebras205 ms283 ms100%289
23inference-net206 ms459 ms100%289
24openai212 ms303 ms100%289
25perplexity219 ms288 ms100%289
26minimax222 ms256 ms100%289
27iflytek232 ms902 ms99.7%289
28anthropic243 ms330 ms100%289
29sarvam252 ms264 ms100%289
30reka274 ms632 ms100%289
31writer275 ms378 ms100%289
32friendli278 ms479 ms100%289
33targon317 ms334 ms100%289
34mistral321 ms388 ms100%289
35ai21342 ms471 ms100%289
36stepfun344 ms960 ms100%289
37siliconflow373 ms399 ms100%289
38sensenova442 ms1137 ms100%289
39deepinfra452 ms1060 ms100%289
40nebius479 ms526 ms100%289
41hyperbolic482 ms570 ms100%289
42doubao492 ms1223 ms99.7%289
43featherless496 ms1493 ms100%289
44nscale544 ms548 ms100%289
45aleph-alpha552 ms619 ms100%289
46hunyuan1116 ms1125 ms100%289

fireworks leads by 9 ms over sambanova here. The median provider measured from Asia (Tokyo) answers in 212 ms, so the spread between the fastest and a typical option is 195 ms on every single request — before the model has produced anything.

Inference latency (time-to-first-token)

Each provider is measured on the model named below — model size affects TTFT far more than the network does, so these numbers are not a like-for-like ranking of providers. Use the edge-latency table above for that. Coverage is limited to providers we hold an API key for.

First model token (TTFT) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics
First model token (TTFT)Wait until a streamed model response emits its first token.
Typical · p5050% of successful timed samples finish within this time.
Slower · p9595% of successful timed samples finish within this time.

Models differ between providers; compare each named model over time.

#ProviderModelTypical (p50 TTFT)Slower (p95)Samples
1typesafejev-1.13.0850 ms1050 ms72
2groqopenai/gpt-oss-120b1455 ms1772 ms72
3googlegemini-flash-lite-latest1761 ms8059 ms72

Why measure from Asia (Tokyo) separately?

Latency is a property of a route, not of a company. The same provider can lead in one region and trail in another, so a ranking produced from a single location tells you very little about what your users will experience somewhere else. This page reports only what was measured from Asia (Tokyo); the other regions are ranked independently and often disagree — see the cross-region summary for how far apart they get.

How should these numbers be read?

p50 is the typical request and p95 is the slow tail: if p95 is far above p50, that provider is inconsistent from here, which usually hurts more than a slightly higher median. Uptime counts a probe as failed only on a genuine service failure — an authentication error means the endpoint answered correctly and counts as up. All figures cover the last 24 hours and are recomputed continuously; the methodology page states the limits of this data plainly.