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