60 пар рынков · ms RTT
Межрыночная задержка
Опубликованные времена туда-обратно между рынками — третий критерий решений по размещению после цены и мощности.
| Из | В | RTT, ms | Источник |
|---|---|---|---|
| Amsterdam | N. Virginia | 85 | Azure network round-trip latency statistics, Jul 2026 (West Europe ↔ East US) |
| Bangkok | Kuala Lumpur | 30 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-5) |
| Bangkok | Jakarta | 52 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-3) |
| Bangkok | Mumbai | 92 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-south-1) |
| Bangkok | Seoul | 97 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-northeast-2) |
| Bangkok | Tokyo | 99 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-northeast-1) |
| Bangkok | Dubai | 124 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ me-central-1) |
| Bangkok | Sydney | 126 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ ap-southeast-2) |
| Bangkok | Frankfurt | 192 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ eu-central-1) |
| Bangkok | London | 194 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ eu-west-2) |
| Bangkok | Dallas | 221 | WonderNetwork global ping statistics (Bangkok ↔ Dallas) |
| Bangkok | N. Virginia | 254 | cloudping.co — AWS inter-region latency (ap-southeast-7 ↔ us-east-1) |
| Frankfurt | Amsterdam | 11 | Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ West Europe) |
| Frankfurt | London | 16 | Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ UK South) |
| Frankfurt | Dubai | 118 | Azure network round-trip latency statistics, Jul 2026 (Germany West Central ↔ UAE North) |
| Jakarta | Mumbai | 68 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Central India) |
| Jakarta | Seoul | 80 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Korea Central) |
| Jakarta | Tokyo | 85 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Japan East) |
| Jakarta | Dubai | 96 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ UAE North) |
| Jakarta | Sydney | 108 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Australia East) |
| Jakarta | Frankfurt | 171 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ Germany West Central) |
| Jakarta | Amsterdam | 172 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ West Europe) |
| Jakarta | London | 182 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ UK South) |
| Jakarta | Dallas | 214 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ South Central US) |
| Jakarta | N. Virginia | 237 | Azure network round-trip latency statistics, Jul 2026 (Indonesia Central ↔ East US) |
| Kuala Lumpur | Jakarta | 21 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Indonesia Central) |
| Kuala Lumpur | Mumbai | 59 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Central India) |
| Kuala Lumpur | Seoul | 69 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Korea Central) |
| Kuala Lumpur | Tokyo | 77 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Japan East) |
| Kuala Lumpur | Dubai | 87 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ UAE North) |
| Kuala Lumpur | Sydney | 100 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Australia East) |
| Kuala Lumpur | Frankfurt | 162 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ Germany West Central) |
| Kuala Lumpur | Amsterdam | 166 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ West Europe) |
| Kuala Lumpur | London | 173 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ UK South) |
| Kuala Lumpur | Dallas | 206 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ South Central US) |
| Kuala Lumpur | N. Virginia | 229 | Azure network round-trip latency statistics, Jul 2026 (Malaysia West ↔ East US) |
| London | Amsterdam | 11 | Azure network round-trip latency statistics, Jul 2026 (UK South ↔ West Europe) |
| London | N. Virginia | 78 | Azure network round-trip latency statistics, Jul 2026 (UK South ↔ East US) |
| Mumbai | Dubai | 32 | Azure network round-trip latency statistics, Jul 2026 (Central India ↔ UAE North) |
| Mumbai | Frankfurt | 140 | Azure network round-trip latency statistics, Jul 2026 (Central India ↔ Germany West Central) |
| N. Virginia | Dallas | 35 | Azure network round-trip latency statistics, Jul 2026 (East US ↔ South Central US) |
| Seoul | N. Virginia | 185 | Azure network round-trip latency statistics, Jul 2026 (Korea Central ↔ East US) |
| Singapore | Kuala Lumpur | 8 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Malaysia West) |
| Singapore | Jakarta | 16 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Indonesia Central) |
| Singapore | Bangkok | 29 | cloudping.co — AWS inter-region latency (ap-southeast-1 ↔ ap-southeast-7) |
| Singapore | Mumbai | 53 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Central India) |
| Singapore | Seoul | 68 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Korea Central) |
| Singapore | Tokyo | 72 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Japan East) |
| Singapore | Dubai | 83 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ UAE North) |
| Singapore | Sydney | 95 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Australia East) |
| Singapore | Frankfurt | 167 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ Germany West Central) |
| Singapore | London | 167 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ UK South) |
| Singapore | Amsterdam | 169 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ West Europe) |
| Singapore | Dallas | 200 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ South Central US) |
| Singapore | N. Virginia | 224 | Azure network round-trip latency statistics, Jul 2026 (Southeast Asia ↔ East US) |
| Sydney | N. Virginia | 202 | Azure network round-trip latency statistics, Jul 2026 (Australia East ↔ East US) |
| Tokyo | Seoul | 29 | Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ Korea Central) |
| Tokyo | Sydney | 103 | Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ Australia East) |
| Tokyo | Dallas | 129 | Azure network round-trip latency statistics, Jul 2026 (Japan East ↔ South Central US) |
| Tokyo | N. Virginia | 162 | Azure 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.