BitMEX

Where Are BitMEX's Servers Located?

BitMEX responds fastest from the AWS London region (eu-west-1) — about 26 ms round-trip for a REST call, which places its API infrastructure in or near London. From Seoul, the slowest measured region, the same call takes around 362 ms — 14× slower. Picking the right server location is the single biggest latency win available when trading on BitMEX.

Measured latency to BitMEX around the world

REST ticker round-trip from eight AWS regions

Seoul · 362 ms Hong Kong · 341 ms Tokyo · 317 ms Singapore · 280 ms N. California · 226 ms N. Virginia · 166 ms Frankfurt · 43 ms London · 26 ms

BitMEX latency from eight AWS regions

AWS region Round-trip
London eu-west-1 ~26 ms
Frankfurt eu-central-1 ~43 ms
N. Virginia us-east-1 ~166 ms
N. California us-west-1 ~226 ms
Singapore ap-southeast-1 ~280 ms
Tokyo ap-northeast-1 ~317 ms
Hong Kong ap-east-1 ~341 ms
Seoul ap-northeast-2 ~362 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 BitMEX

Host your trading server or bot in AWS London (eu-west-1): it reaches BitMEX in about 26 ms, fast enough that order placement and market data stay effectively real-time.

Avoid running latency-sensitive strategies against BitMEX from Seoul or other distant regions. At ~362 ms (14× 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 BitMEX 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 BitMEX from London 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 BitMEX's servers located?

BitMEX responds fastest from AWS London (eu-west-1) — about 26 ms round-trip — which places its API infrastructure in or near London.

What is the best server location for BitMEX?

AWS London (eu-west-1). A server there reaches BitMEX in ~26 ms, versus ~362 ms from Seoul — a 14× difference on every API call.

How much does server location change latency to BitMEX?

In our measurements: ~26 ms from London versus ~362 ms from Seoul — a 14× spread. Every order and every orderbook update pays this tax in both directions.

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

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

An unhandled error has occurred. Reload X

Reconnecting…

Retrying in s…

Reconnecting…

Session paused

Reloading…