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