Measured latency to Binance.US around the world
REST ticker round-trip from eight AWS regions
Binance.US latency from eight AWS regions
| AWS region | Round-trip |
|---|---|
| N. Virginia us-east-1 | ~78 ms |
| London eu-west-1 | ~95 ms |
| N. California us-west-1 | ~99 ms |
| Frankfurt eu-central-1 | ~128 ms |
| Tokyo ap-northeast-1 | ~206 ms |
| Seoul ap-northeast-2 | ~277 ms |
| Hong Kong ap-east-1 | ~298 ms |
| Singapore ap-southeast-1 | ~383 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 Binance.US
Host your trading server or bot in AWS N. Virginia (us-east-1): it reaches Binance.US in about 78 ms, fast enough that order placement and market data stay effectively real-time.
Avoid running latency-sensitive strategies against Binance.US from Singapore or other distant regions. At ~383 ms (5× 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
Mercado Bitcoin server location
~61 ms
Foxbit server location
~62 ms
Bitso server location
~121 ms
Upbit server location
~10 msFrequently asked questions
Where are Binance.US's servers located?
Binance.US responds fastest from AWS N. Virginia (us-east-1) — about 78 ms round-trip — which places its API infrastructure in or near N. Virginia.
What is the best server location for Binance.US?
AWS N. Virginia (us-east-1). A server there reaches Binance.US in ~78 ms, versus ~383 ms from Singapore — a 5× difference on every API call.
How much does server location change latency to Binance.US?
In our measurements: ~78 ms from N. Virginia versus ~383 ms from Singapore — a 5× spread. Every order and every orderbook update pays this tax in both directions.