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