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