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