Moscow network latency (MOW)
Round-trip measurements between Moscow (MOW) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.
Moscow (MOW) is the easternmost European PoP in this dataset. The tables compare its European routes with longer intercontinental paths.
Measurement round: 2026-08-16T04:07:28Z.
The published round covers 19 outbound routes from Moscow. Incoming routes are measured separately; neither direction describes last-mile performance.
Fastest routes from Moscow
Average round-trip time Β· lowest first
- Berlin BER27.5 ms
- Frankfurt FRA35.9 ms
- Amsterdam AMS37.6 ms
- London LON42.4 ms
- Paris PAR44.0 ms
- Marseille MRS49.9 ms
- New York NYC107.5 ms
- Ashburn IAD113.9 ms
- Hong Kong HKG118.6 ms
- Taipei TPE132.1 ms
9 more routes
- Miami MIA144.5 ms
- Singapore SIN147.3 ms
- Tokyo TYO162.2 ms
- Seattle SEA164.8 ms
- Los Angeles LAX177.7 ms
- Johannesburg JNB201.9 ms
- SΓ£o Paulo GRU214.4 ms
- Melbourne MEL235.9 ms
- Sydney SYD241.8 ms
Minimum, maximum and variation
| PoP | Min | Max | Stdev |
|---|---|---|---|
| Berlin | 26.72 | 29.96 | 0.74 |
| Frankfurt | 33.56 | 42.93 | 1.78 |
| Amsterdam | 37.09 | 39.90 | 0.57 |
| London | 40.38 | 48.72 | 1.83 |
| Paris | 42.02 | 49.11 | 1.64 |
| Marseille | 47.94 | 53.35 | 1.46 |
| New York | 103.90 | 121.54 | 3.46 |
| Ashburn | 107.82 | 129.74 | 5.37 |
| Hong Kong | 116.41 | 127.80 | 2.24 |
| Taipei | 126.75 | 145.67 | 4.52 |
| Miami | 138.89 | 163.99 | 5.03 |
| Singapore | 144.41 | 156.92 | 2.32 |
| Tokyo | 152.69 | 185.56 | 6.91 |
| Seattle | 155.86 | 193.38 | 7.90 |
| Los Angeles | 173.78 | 191.21 | 3.21 |
| Johannesburg | 192.01 | 232.17 | 7.94 |
| SΓ£o Paulo | 203.61 | 257.23 | 10.55 |
| Melbourne | 223.93 | 262.01 | 8.78 |
| Sydney | 231.04 | 265.67 | 7.65 |
Fastest routes into Moscow
Average round-trip time Β· lowest first
- Berlin BER28.6 ms
- Frankfurt FRA34.7 ms
- Amsterdam AMS38.1 ms
- London LON43.5 ms
- Paris PAR44.7 ms
- Marseille MRS49.6 ms
- New York NYC107.0 ms
- Ashburn IAD112.8 ms
- Hong Kong HKG118.2 ms
- Taipei TPE132.7 ms
9 more routes
- Miami MIA145.5 ms
- Singapore SIN147.7 ms
- Tokyo TYO161.7 ms
- Seattle SEA164.6 ms
- Los Angeles LAX177.0 ms
- Johannesburg JNB200.7 ms
- SΓ£o Paulo GRU219.5 ms
- Melbourne MEL236.1 ms
- Sydney SYD242.2 ms
Minimum, maximum and variation
| PoP | Min | Max | Stdev |
|---|---|---|---|
| Berlin | 27.35 | 31.58 | 1.10 |
| Frankfurt | 32.66 | 40.02 | 1.68 |
| Amsterdam | 35.69 | 44.57 | 1.90 |
| London | 41.81 | 48.52 | 1.38 |
| Paris | 43.04 | 51.46 | 1.56 |
| Marseille | 47.26 | 58.00 | 2.18 |
| New York | 101.46 | 119.28 | 4.26 |
| Ashburn | 109.18 | 122.64 | 3.63 |
| Hong Kong | 115.72 | 128.25 | 2.23 |
| Taipei | 127.77 | 145.28 | 3.91 |
| Miami | 142.62 | 152.94 | 2.55 |
| Singapore | 144.38 | 154.89 | 2.64 |
| Tokyo | 155.32 | 174.84 | 4.83 |
| Seattle | 158.38 | 192.70 | 7.23 |
| Los Angeles | 169.62 | 197.78 | 6.43 |
| Johannesburg | 196.07 | 218.52 | 4.34 |
| SΓ£o Paulo | 208.05 | 246.05 | 7.63 |
| Melbourne | 226.33 | 266.71 | 8.22 |
| Sydney | 230.07 | 270.93 | 9.04 |
RTT and geographic distance
Location
- Location: Moscow, Russia (Europe)
- Region: Europe
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 524901; 55.75204, 37.61781
- Coverage: RTT measurements to 19 other PoPs across 5 continents
Interconnection
- Facility: MOW1
- Upstream transit: RETN / Melbicom
Round Summary
| Metric | Value |
|---|---|
| Fastest Route | π·πΊ Moscow (MOW) β π©πͺ Berlin (BER) (27.5 ms); Ultra-Low |
| Slowest Route | π·πΊ Moscow (MOW) β π¦πΊ Sydney (SYD) (241.8 ms) |
| Average RTT | 126.3 ms |
| Average Jitter | 1.03 ms |
| Average Packet Loss | 0.06% |
| Best Fiber Efficiency | 68.6% |
| Intra-Region Peers | 6 PoPs in Europe |
| Total Routes | 19 outbound / 19 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
Regional Routes
Moscow's 6 other Europe PoPs have RTTs from 27.5 ms (Berlin (BER)) to 49.9 ms (Marseille (MRS)).
Moscow is in western Russia and is the easternmost European city in this dataset.
Outbound Latency from Moscow (MOW)
Round-trip time in milliseconds from Moscow to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| π©πͺ Berlin (BER) | 27.5 | 15.8 ms | 57.5% | 0.3 ms | 0.13% | Ultra-Low |
| π©πͺ Frankfurt (FRA) | 35.9 | 19.85 ms | 55.3% | 0.3 ms | 0% | Excellent |
| π³π± Amsterdam (AMS) | 37.6 | 21.1 ms | 56.1% | 0.28 ms | 0.17% | Excellent |
| π¬π§ London (LON) | 42.4 | 24.56 ms | 57.9% | 0.46 ms | 0.18% | Excellent |
| π«π· Paris (PAR) | 44 | 24.42 ms | 55.5% | 0.29 ms | 0% | Excellent |
| π«π· Marseille (MRS) | 49.9 | 26.23 ms | 52.6% | 0.4 ms | 0.05% | Excellent |
| πΊπΈ New York (NYC) | 107.5 | 73.75 ms | 68.6% | 1 ms | 0% | Good |
| πΊπΈ Ashburn (IAD) | 113.9 | 76.88 ms | 67.5% | 1 ms | 0.08% | Good |
| ππ° Hong Kong (HKG) | 118.6 | 70.05 ms | 59.1% | 0.77 ms | 0.13% | Good |
| πΉπΌ Taipei (TPE) | 132.1 | 72.16 ms | 54.6% | 1.49 ms | 0% | Good |
| πΊπΈ Miami (MIA) | 144.5 | 90.48 ms | 62.6% | 1.25 ms | 0.07% | Good |
| πΈπ¬ Singapore (SIN) | 147.3 | 82.49 ms | 56% | 1.11 ms | 0.17% | Good |
| π―π΅ Tokyo (TYO) | 162.2 | 73.42 ms | 45.3% | 1.92 ms | 0.08% | Fair |
| πΊπΈ Seattle (SEA) | 164.8 | 82.23 ms | 49.9% | 0.99 ms | 0% | Fair |
| πΊπΈ Los Angeles (LAX) | 177.7 | 95.9 ms | 54% | 1.55 ms | 0% | Fair |
| πΏπ¦ Johannesburg (JNB) | 201.9 | 89.37 ms | 44.3% | 1.29 ms | 0% | Fair |
| π§π· SΓ£o Paulo (GRU) | 214.4 | 115.47 ms | 53.9% | 1.47 ms | 0% | Fair |
| π¦πΊ Melbourne (MEL) | 235.9 | 141.13 ms | 59.8% | 1.11 ms | 0% | Fair |
| π¦πΊ Sydney (SYD) | 241.8 | 141.84 ms | 58.7% | 2.66 ms | 0% | Fair |
Fastest Routes to Moscow (MOW)
The 10 fastest measured routes to Moscow, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.
| Rank | Source | Avg RTT | Min | Max | Stdev |
|---|---|---|---|---|---|
| 1 | π©πͺ Berlin (BER) | 28.6 ms | 27.35 ms | 31.58 ms | 1.1 ms |
| 2 | π©πͺ Frankfurt (FRA) | 34.7 ms | 32.66 ms | 40.02 ms | 1.68 ms |
| 3 | π³π± Amsterdam (AMS) | 38.1 ms | 35.69 ms | 44.57 ms | 1.9 ms |
| 4 | π¬π§ London (LON) | 43.5 ms | 41.81 ms | 48.52 ms | 1.38 ms |
| 5 | π«π· Paris (PAR) | 44.7 ms | 43.04 ms | 51.46 ms | 1.56 ms |
| 6 | π«π· Marseille (MRS) | 49.6 ms | 47.26 ms | 58 ms | 2.18 ms |
| 7 | πΊπΈ New York (NYC) | 107 ms | 101.46 ms | 119.28 ms | 4.26 ms |
| 8 | πΊπΈ Ashburn (IAD) | 112.8 ms | 109.18 ms | 122.64 ms | 3.63 ms |
| 9 | ππ° Hong Kong (HKG) | 118.2 ms | 115.72 ms | 128.25 ms | 2.23 ms |
| 10 | πΉπΌ Taipei (TPE) | 132.7 ms | 127.77 ms | 145.28 ms | 3.91 ms |
Inbound Latency to Moscow (MOW)
Round-trip time in milliseconds from all other PoPs to Moscow. The measurement origin matters: inbound and outbound RTT can differ for the same pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| π©πͺ Berlin (BER) | 28.6 | 15.8 ms | 55.2% | 0.33 ms | 0% | Ultra-Low |
| π©πͺ Frankfurt (FRA) | 34.7 | 19.85 ms | 57.2% | 0.25 ms | 0.13% | Excellent |
| π³π± Amsterdam (AMS) | 38.1 | 21.1 ms | 55.4% | 0.38 ms | 0% | Excellent |
| π¬π§ London (LON) | 43.5 | 24.56 ms | 56.5% | 0.2 ms | 0.06% | Excellent |
| π«π· Paris (PAR) | 44.7 | 24.42 ms | 54.6% | 0.23 ms | 0.2% | Excellent |
| π«π· Marseille (MRS) | 49.6 | 26.23 ms | 52.9% | 0.45 ms | 0.07% | Excellent |
| πΊπΈ New York (NYC) | 107 | 73.75 ms | 68.9% | 1.08 ms | 0.06% | Good |
| πΊπΈ Ashburn (IAD) | 112.8 | 76.88 ms | 68.2% | 0.79 ms | 0.13% | Good |
| ππ° Hong Kong (HKG) | 118.2 | 70.05 ms | 59.3% | 1.17 ms | 0.11% | Good |
| πΉπΌ Taipei (TPE) | 132.7 | 72.16 ms | 54.4% | 0.68 ms | 0.09% | Good |
| πΊπΈ Miami (MIA) | 145.5 | 90.48 ms | 62.2% | 1.67 ms | 0.13% | Good |
| πΈπ¬ Singapore (SIN) | 147.7 | 82.49 ms | 55.8% | 0.99 ms | 0.11% | Good |
| π―π΅ Tokyo (TYO) | 161.7 | 73.42 ms | 45.4% | 1.62 ms | 0.09% | Fair |
| πΊπΈ Seattle (SEA) | 164.6 | 82.23 ms | 50% | 1.42 ms | 0% | Fair |
| πΊπΈ Los Angeles (LAX) | 177 | 95.9 ms | 54.2% | 1.7 ms | 0% | Fair |
| πΏπ¦ Johannesburg (JNB) | 200.7 | 89.37 ms | 44.5% | 2.17 ms | 0.16% | Fair |
| π§π· SΓ£o Paulo (GRU) | 219.5 | 115.47 ms | 52.6% | 1.57 ms | 0% | Fair |
| π¦πΊ Melbourne (MEL) | 236.1 | 141.13 ms | 59.8% | 2.48 ms | 0.05% | Fair |
| π¦πΊ Sydney (SYD) | 242.2 | 141.84 ms | 58.6% | 1.9 ms | 0.11% | Fair |
Europe Peers
Moscow is one of 7 Hats Network PoPs in Europe. The table lists outbound measurements within the region.
| PoP | Code | Country | RTT (ms) | Tier |
|---|---|---|---|---|
| π³π± Amsterdam (AMS) | AMS | Netherlands | 37.6 | Excellent |
| π©πͺ Berlin (BER) | BER | Germany | 27.5 | Ultra-Low |
| π©πͺ Frankfurt (FRA) | FRA | Germany | 35.9 | Excellent |
| π¬π§ London (LON) | LON | UK | 42.4 | Excellent |
| π«π· Marseille (MRS) | MRS | France | 49.9 | Excellent |
| π«π· Paris (PAR) | PAR | France | 44 | Excellent |
Questions
What is the fastest route to Moscow?
The fastest measured route to Moscow (MOW) is Berlin (BER) β Moscow (MOW), averaging 28.6 ms RTT (Ultra-Low).
What is the fastest route from Moscow?
The fastest measured route from Moscow (MOW) is Moscow (MOW) β Berlin (BER), averaging 27.5 ms RTT (Ultra-Low).
How well connected is Moscow to the Hats Network backbone?
Moscow (MOW) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, Moscow (MOW) β Sydney (SYD), averages 241.8 ms RTT.
Round published August 16, 2026. All 20 PoPs Β· Dataset and licence.
Marseille network latency (MRS)
Round-trip measurements between Marseille (MRS) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.
Paris network latency (PAR)
Round-trip measurements between Paris (PAR) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.