▮▮Coloprice

60 market pairs · ms RTT

Inter-market latency

Published round-trip times between markets — the third axis of placement decisions after price and power.

FromToRTT, msSource
AmsterdamN. Virginia85Azure network round-trip latency statistics, Jul 2026 (West Europe ↔ East US)
BangkokKuala Lumpur30cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-5)
BangkokJakarta52cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-3)
BangkokMumbai92cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-south-1)
BangkokSeoul97cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-northeast-2)
BangkokTokyo99cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-northeast-1)
BangkokDubai124cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ me-central-1)
BangkokSydney126cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-2)
BangkokFrankfurt192cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ eu-central-1)
BangkokLondon194cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ eu-west-2)
BangkokDallas221WonderNetwork global ping statistics (Bangkok ↔ Dallas)
BangkokN. Virginia254cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ us-east-1)
FrankfurtAmsterdam11Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ West Europe)
FrankfurtLondon16Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ UK South)
FrankfurtDubai118Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ UAE North)
JakartaMumbai68Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Central India)
JakartaSeoul80Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Korea Central)
JakartaTokyo85Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Japan East)
JakartaDubai96Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ UAE North)
JakartaSydney108Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Australia East)
JakartaFrankfurt171Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Germany West Central)
JakartaAmsterdam172Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ West Europe)
JakartaLondon182Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ UK South)
JakartaDallas214Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ South Central US)
JakartaN. Virginia237Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ East US)
Kuala LumpurJakarta21Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Indonesia Central)
Kuala LumpurMumbai59Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Central India)
Kuala LumpurSeoul69Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Korea Central)
Kuala LumpurTokyo77Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Japan East)
Kuala LumpurDubai87Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ UAE North)
Kuala LumpurSydney100Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Australia East)
Kuala LumpurFrankfurt162Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Germany West Central)
Kuala LumpurAmsterdam166Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ West Europe)
Kuala LumpurLondon173Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ UK South)
Kuala LumpurDallas206Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ South Central US)
Kuala LumpurN. Virginia229Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ East US)
LondonAmsterdam11Azure network round-trip latency statistics, Jul 2026 (UK South ↔ West Europe)
LondonN. Virginia78Azure network round-trip latency statistics, Jul 2026 (UK South ↔ East US)
MumbaiDubai32Azure network round-trip latency statistics, Jul 2026 (Central India ↔ UAE North)
MumbaiFrankfurt140Azure network round-trip latency statistics, Jul 2026 (Central India ↔ Germany West Central)
N. VirginiaDallas35Azure network round-trip latency statistics, Jul 2026 (East US ↔ South Central US)
SeoulN. Virginia185Azure network round-trip latency statistics, Jul 2026 (Korea Central ↔ East US)
SingaporeKuala Lumpur8Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Malaysia West)
SingaporeJakarta16Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Indonesia Central)
SingaporeBangkok29cloudping.co — AWS inter-region latency (ap-southeast-1 ↔ ap-southeast-7)
SingaporeMumbai53Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Central India)
SingaporeSeoul68Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Korea Central)
SingaporeTokyo72Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Japan East)
SingaporeDubai83Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ UAE North)
SingaporeSydney95Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Australia East)
SingaporeFrankfurt167Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Germany West Central)
SingaporeLondon167Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ UK South)
SingaporeAmsterdam169Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ West Europe)
SingaporeDallas200Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ South Central US)
SingaporeN. Virginia224Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ East US)
SydneyN. Virginia202Azure network round-trip latency statistics, Jul 2026 (Australia East ↔ East US)
TokyoSeoul29Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ Korea Central)
TokyoSydney103Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ Australia East)
TokyoDallas129Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ South Central US)
TokyoN. Virginia162Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ East US)

Latencies are round-trip times (RTT) between cloud regions or measurement servers located in or near each market, not between specific colocation facilities. Azure figures are monthly P50 (median) round-trip times measured between Azure regions over the 30-day window ending July 30, 2026; city names are mapped to the nearest Azure region (Singapore = Southeast Asia, Kuala Lumpur = Malaysia West, Jakarta = Indonesia Central, Tokyo = Japan East, Seoul = Korea Central, Mumbai = Central India (Pune, ~120 km from Mumbai), Sydney = Australia East, Frankfurt = Germany West Central, London = UK South, Amsterdam = West Europe, Dubai = UAE North, N. Virginia = East US, Dallas = South Central US (San Antonio, TX)). Bangkok figures come from cloudping.co, which measures TCP round-trip latency between AWS regions every 6 hours (Bangkok = ap-southeast-7, opened January 2025); the Bangkok–Dallas pair uses WonderNetwork server-to-server ping averages, as neither AWS nor Azure publishes that route. Actual latency between two specific data centers depends on carrier, route and peering, and can differ by several milliseconds (or more on poorly peered routes) from these cloud-backbone figures, which generally represent near-optimal paths over private fiber.