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