LBank

Where Are LBank's Servers Located?

LBank responds fastest from the AWS Hong Kong region (ap-east-1) — about 18 ms round-trip for a REST call, which places its API infrastructure in or near Hong Kong. From London, the slowest measured region, the same call takes around 372 ms — 21× slower. Picking the right server location is the single biggest latency win available when trading on LBank.

Measured latency to LBank around the world

REST ticker round-trip from eight AWS regions

London · 372 ms N. Virginia · 360 ms Frankfurt · 323 ms N. California · 247 ms Seoul · 140 ms Tokyo · 107 ms Singapore · 104 ms Hong Kong · 18 ms

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.

Trade on LBank with a co-located server

Arbitron runs every account on its own dedicated trading server with its own IP, and you are able to choose the server region — so your orders reach LBank from Hong Kong in milliseconds, with no shared infrastructure and no extra hops.

Compare with other exchanges

All exchange server locations and latencies →

Frequently 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.

Can I trade on LBank with a co-located server?

Yes. LBank is supported by Arbitron: each account gets a dedicated trading server with a selectable region, placed next to the exchanges you trade.

Reconnecting…

Retrying in s…

Reconnecting…

Arbitron is updating. Back in a few seconds…

No internet connection. Waiting to reconnect…

Session paused

Reloading…

Something went wrong on this page. Arbitron is updating. This page will reload itself once the new version is up… No internet connection. Waiting to reconnect… Reload