Measured latency to EXMO around the world
REST ticker round-trip from eight AWS regions
EXMO latency from eight AWS regions
| AWS region | Round-trip |
|---|---|
| Frankfurt eu-central-1 | ~24 ms |
| London eu-west-1 | ~57 ms |
| N. Virginia us-east-1 | ~238 ms |
| Singapore ap-southeast-1 | ~280 ms |
| N. California us-west-1 | ~311 ms |
| Hong Kong ap-east-1 | ~348 ms |
| Tokyo ap-northeast-1 | ~427 ms |
| Seoul ap-northeast-2 | ~479 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 EXMO
Host your trading server or bot in AWS Frankfurt (eu-central-1): it reaches EXMO in about 24 ms, fast enough that order placement and market data stay effectively real-time.
Avoid running latency-sensitive strategies against EXMO from Seoul or other distant regions. At ~479 ms (20× 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
Kraken server location
~18 ms
Bitstamp server location
~20 ms
Bitfinex server location
~22 msFrequently asked questions
Where are EXMO's servers located?
EXMO responds fastest from AWS Frankfurt (eu-central-1) — about 24 ms round-trip — which places its API infrastructure in or near Frankfurt.
What is the best server location for EXMO?
AWS Frankfurt (eu-central-1). A server there reaches EXMO in ~24 ms, versus ~479 ms from Seoul — a 20× difference on every API call.
How much does server location change latency to EXMO?
In our measurements: ~24 ms from Frankfurt versus ~479 ms from Seoul — a 20× spread. Every order and every orderbook update pays this tax in both directions.