🇷🇺 Moscow Ping & Network Latency (MOW) | AS203314
Moscow (MOW) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 Hats Network (AS203314) backbone PoPs.
🇷🇺 Moscow (MOW)
Moscow anchors Hats Network's reach into Eastern Europe and Central Asia, providing a critical transit corridor between European and Asia-Pacific networks.
This page provides round-trip time (RTT) latency metrics between the Moscow (MOW) PoP and every other node on the Hats Network (AS203314) global backbone.
PoP Highlights
- 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 18 other PoPs across 4 continents
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇷🇺 Moscow (MOW) → 🇩🇪 Berlin (BER) (26.8 ms) — Ultra-Low |
| Slowest Route | 🇷🇺 Moscow (MOW) → 🇦🇺 Sydney (SYD) (244.2 ms) |
| Average RTT | 123.0 ms |
| Average Jitter | 0.91 ms |
| Average Packet Loss | 0.06% |
| Best Fiber Efficiency | 69.6% |
| Intra-Region Peers | 6 PoPs in Europe |
| Total Routes | 18 outbound / 18 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
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) | 26.8 | 15.8 ms | 59% | 0.25 ms | 0.18% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | 34.2 | 19.85 ms | 58% | 0.18 ms | 0.01% | Excellent |
| 🇳🇱 Amsterdam (AMS) | 38.8 | 21.1 ms | 54.4% | 0.26 ms | 0% | Excellent |
| 🇫🇷 Paris (PAR) | 43.7 | 24.42 ms | 55.9% | 0.27 ms | 0.1% | Excellent |
| 🇬🇧 London (LON) | 44 | 24.56 ms | 55.8% | 0.31 ms | 0% | Excellent |
| 🇫🇷 Marseille (MRS) | 51.1 | 26.23 ms | 51.3% | 0.6 ms | 0.04% | Excellent |
| 🇺🇸 New York (NYC) | 106 | 73.75 ms | 69.6% | 1.01 ms | 0.17% | Good |
| 🇺🇸 Ashburn (IAD) | 112.6 | 76.88 ms | 68.3% | 0.81 ms | 0.09% | Good |
| 🇭🇰 Hong Kong (HKG) | 121.1 | 70.05 ms | 57.8% | 1.31 ms | 0.04% | Good |
| 🇹🇼 Taipei (TPE) | 133 | 72.16 ms | 54.3% | 0.73 ms | 0% | Good |
| 🇺🇸 Miami (MIA) | 144.7 | 90.48 ms | 62.5% | 0.72 ms | 0.08% | Good |
| 🇸🇬 Singapore (SIN) | 149.5 | 82.49 ms | 55.2% | 1.17 ms | 0.11% | Good |
| 🇯🇵 Tokyo (TYO) | 165.3 | 73.42 ms | 44.4% | 1.38 ms | 0.03% | Fair |
| 🇺🇸 Seattle (SEA) | 166.1 | 82.23 ms | 49.5% | 1.17 ms | 0% | Fair |
| 🇺🇸 Los Angeles (LAX) | 173.8 | 95.9 ms | 55.2% | 1.22 ms | 0.1% | Fair |
| 🇧🇷 São Paulo (GRU) | 219.4 | 115.47 ms | 52.6% | 1.41 ms | 0.04% | Fair |
| 🇦🇺 Melbourne (MEL) | 238.9 | 141.13 ms | 59.1% | 2.12 ms | 0.05% | Fair |
| 🇦🇺 Sydney (SYD) | 244.2 | 141.84 ms | 58.1% | 1.43 ms | 0% | Fair |
Inbound Latency to Moscow (MOW)
Round-trip time in milliseconds from all other PoPs to Moscow. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇩🇪 Berlin (BER) | 28.5 | 15.8 ms | 55.4% | 0.19 ms | 0.12% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | 34.6 | 19.85 ms | 57.4% | 0.25 ms | 0.06% | Excellent |
| 🇳🇱 Amsterdam (AMS) | 38 | 21.1 ms | 55.5% | 0.23 ms | 0% | Excellent |
| 🇬🇧 London (LON) | 42.7 | 24.56 ms | 57.5% | 0.44 ms | 0% | Excellent |
| 🇫🇷 Paris (PAR) | 43.9 | 24.42 ms | 55.6% | 0.24 ms | 0% | Excellent |
| 🇫🇷 Marseille (MRS) | 51.4 | 26.23 ms | 51% | 0.39 ms | 0% | Excellent |
| 🇺🇸 New York (NYC) | 107.5 | 73.75 ms | 68.6% | 1.24 ms | 0.05% | Good |
| 🇺🇸 Ashburn (IAD) | 113.6 | 76.88 ms | 67.7% | 0.8 ms | 0% | Good |
| 🇭🇰 Hong Kong (HKG) | 119.6 | 70.05 ms | 58.6% | 1.14 ms | 0.14% | Good |
| 🇹🇼 Taipei (TPE) | 132.7 | 72.16 ms | 54.4% | 1.56 ms | 0.14% | Good |
| 🇺🇸 Miami (MIA) | 144.1 | 90.48 ms | 62.8% | 1.69 ms | 0% | Good |
| 🇸🇬 Singapore (SIN) | 148.7 | 82.49 ms | 55.5% | 1.54 ms | 0.14% | Good |
| 🇺🇸 Seattle (SEA) | 164.1 | 82.23 ms | 50.1% | 1.62 ms | 0% | Fair |
| 🇯🇵 Tokyo (TYO) | 165.3 | 73.42 ms | 44.4% | 1.75 ms | 0.08% | Fair |
| 🇺🇸 Los Angeles (LAX) | 173.1 | 95.9 ms | 55.4% | 2.06 ms | 0.07% | Fair |
| 🇧🇷 São Paulo (GRU) | 218.1 | 115.47 ms | 52.9% | 1.15 ms | 0.15% | Fair |
| 🇦🇺 Melbourne (MEL) | 238.1 | 141.13 ms | 59.3% | 2.48 ms | 0.09% | Fair |
| 🇦🇺 Sydney (SYD) | 243.4 | 141.84 ms | 58.3% | 2.78 ms | 0% | Fair |
Europe Peers
Moscow is one of 7 Hats Network PoPs in Europe. Intra-region routes offer the lowest latency and highest path diversity.
| PoP | Code | Country | RTT (ms) | Tier |
|---|---|---|---|---|
| 🇳🇱 Amsterdam (AMS) | AMS | Netherlands | 38.8 | Excellent |
| 🇩🇪 Berlin (BER) | BER | Germany | 26.8 | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | FRA | Germany | 34.2 | Excellent |
| 🇬🇧 London (LON) | LON | UK | 44 | Excellent |
| 🇫🇷 Marseille (MRS) | MRS | France | 51.1 | Excellent |
| 🇫🇷 Paris (PAR) | PAR | France | 43.7 | Excellent |
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 19 PoPs.
🇫🇷 Marseille Ping & Network Latency (MRS) | AS203314
Marseille (MRS) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 Hats Network (AS203314) backbone PoPs.
🇫🇷 Paris Ping & Network Latency (PAR) | AS203314
Paris (PAR) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 Hats Network (AS203314) backbone PoPs.