Measured latency to Kraken around the world
REST ticker round-trip from eight AWS regions
Kraken latency from eight AWS regions
| AWS region | Round-trip |
|---|---|
| Frankfurt eu-central-1 | ~18 ms |
| Hong Kong ap-east-1 | ~21 ms |
| N. California us-west-1 | ~34 ms |
| Tokyo ap-northeast-1 | ~36 ms |
| Singapore ap-southeast-1 | ~45 ms |
| London eu-west-1 | ~51 ms |
| N. Virginia us-east-1 | ~63 ms |
| Seoul ap-northeast-2 | ~64 ms |
Indicative REST round-trips from our multi-region measurements — for comparing regions, not an SLA. WebSocket feeds are faster in absolute terms, but the regional proportions hold.
Best server location for trading on Kraken
Host your trading server or bot in AWS Frankfurt (eu-central-1): it reaches Kraken in about 18 ms, fast enough that order placement and market data stay effectively real-time.
Avoid running latency-sensitive strategies against Kraken from Seoul or other distant regions. At ~64 ms (4× the co-located figure) every price you see is stale before you can act on it, and that staleness turns into slippage on every market order.
Compare with other exchanges
Bitvavo server location
~15 ms
Bitstamp server location
~20 ms
Bitfinex server location
~22 ms
EXMO server location
~24 msFrequently asked questions
Where are Kraken's servers located?
Kraken responds fastest from AWS Frankfurt (eu-central-1) — about 18 ms round-trip — which places its API infrastructure in or near Frankfurt.
What is the best server location for Kraken?
AWS Frankfurt (eu-central-1). A server there reaches Kraken in ~18 ms, versus ~64 ms from Seoul — a 4× difference on every API call.
How much does server location change latency to Kraken?
In our measurements: ~18 ms from Frankfurt versus ~64 ms from Seoul — a 4× spread. Every order and every orderbook update pays this tax in both directions.