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