Measured latency to NovaDAX around the world
REST ticker round-trip from eight AWS regions
NovaDAX latency from eight AWS regions
| AWS region | Round-trip |
|---|---|
| London eu-west-1 | ~58 ms |
| Frankfurt eu-central-1 | ~64 ms |
| N. Virginia us-east-1 | ~131 ms |
| N. California us-west-1 | ~231 ms |
| Singapore ap-southeast-1 | ~278 ms |
| Tokyo ap-northeast-1 | ~321 ms |
| Hong Kong ap-east-1 | ~341 ms |
| Seoul ap-northeast-2 | ~370 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 NovaDAX
Host your trading server or bot in AWS London (eu-west-1): it reaches NovaDAX in about 58 ms, fast enough that order placement and market data stay effectively real-time.
Avoid running latency-sensitive strategies against NovaDAX from Seoul or other distant regions. At ~370 ms (6× 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
Deribit server location
~10 ms
BitMEX server location
~26 ms
BEQUANT server location
~54 ms
One Trading (Bitpanda Pro) server location
~70 msFrequently asked questions
Where are NovaDAX's servers located?
NovaDAX responds fastest from AWS London (eu-west-1) — about 58 ms round-trip — which places its API infrastructure in or near London.
What is the best server location for NovaDAX?
AWS London (eu-west-1). A server there reaches NovaDAX in ~58 ms, versus ~370 ms from Seoul — a 6× difference on every API call.
How much does server location change latency to NovaDAX?
In our measurements: ~58 ms from London versus ~370 ms from Seoul — a 6× spread. Every order and every orderbook update pays this tax in both directions.