HomeEu hetzner
Data API

Fastest AI API from Europe (Germany)

· edge + inference latency

As of October 22, 2026, measured from Europe (Germany), the fastest AI inference API by edge latency (time-to-first-byte) is fireworks at 97 ms p50 (n=288).

Which AI API is fastest from Europe (Germany)?

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
1fireworks97 ms201 ms99.7%288
2nscale98 ms204 ms99.7%288
3google99 ms202 ms100%288
4openrouter99 ms203 ms100%288
5nebius100 ms295 ms100%288
6meta-llama100 ms295 ms100%288
7aleph-alpha100 ms205 ms100%288
8mistral102 ms298 ms99.3%288
9inference-net194 ms503 ms99.3%288
10baichuan196 ms303 ms100%288
11cerebras198 ms302 ms99.3%288
12baseten199 ms304 ms100%288
13cohere199 ms301 ms100%288
14glm199 ms303 ms100%288
15perplexity200 ms397 ms100%288
16anthropic200 ms303 ms98.6%288
17replicate200 ms406 ms99.0%288
18typesafe200 ms300 ms99.7%288
19reka206 ms501 ms100%288
20yi-01ai230 ms836 ms100%288
21ernie284 ms303 ms100%288
22openai294 ms488 ms99.3%288
23siliconflow295 ms401 ms100%288
24xai295 ms401 ms99.3%288
25sarvam295 ms305 ms100%288
26groq296 ms490 ms99.3%288
27targon297 ms403 ms100%288
28novita297 ms495 ms99.0%288
29writer298 ms498 ms100%288
30together298 ms499 ms99.3%288
31deepseek299 ms403 ms100%288
32kimi299 ms491 ms99.0%288
33iflytek300 ms770 ms100%288
34doubao360 ms823 ms100%288
35sensenova390 ms958 ms100%288
36sambanova397 ms503 ms100%288
37friendli398 ms800 ms100%288
38ai21399 ms600 ms99.7%288
39minimax399 ms600 ms100%288
40qwen401 ms699 ms100%288
41stepfun415 ms1099 ms100%288
42hyperbolic498 ms902 ms98.6%288
43upstage581 ms602 ms100%288
44deepinfra594 ms1096 ms100%288
45featherless700 ms1907 ms99.7%288
46hunyuan1532 ms1598 ms100%288

fireworks leads by 1 ms over nscale here. The median provider measured from Europe (Germany) answers in 295 ms, so the spread between the fastest and a typical option is 198 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
1groqopenai/gpt-oss-120b801 ms1391 ms72
2typesafejev-1.13.0899 ms1499 ms72
3googlegemini-flash-lite-latest1192 ms3983 ms72
4anthropicclaude-haiku-4-50 ms0 ms4
5openaigpt-4o-mini0 ms0 ms1
6cerebrasgpt-oss-120b0 ms0 ms1
7openrouternvidia/nemotron-3-nano-30b-a3b:free0 ms0 ms1

Why measure from Europe (Germany) 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 Europe (Germany); 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.