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