Hats Network | LogoHats Network
BackbonePoP Latency

🇷🇺 Moscow Ping & Network Latency (MOW) | AS203314

Moscow (MOW) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 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.

Measurement round: 2026-08-15T04:03:13Z.

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.

Average RTT from Moscow to every other PoP

Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round

How to read this chart

Each bar is the average round-trip time of one 50-probe ICMP echo round from Moscow (MOW) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.

Full 19-destination dataset
DestinationAvg RTT (ms)Stdev (ms)Distance (km)
Sydney (SYD)243.608.1514,484
Melbourne (MEL)236.108.9114,412
São Paulo (GRU)214.9010.3011,791
Johannesburg (JNB)201.007.119,126
Los Angeles (LAX)174.304.469,793
Seattle (SEA)165.205.338,397
Tokyo (TYO)162.707.427,497
Singapore (SIN)148.307.038,423
Miami (MIA)145.102.969,240
Taipei (TPE)130.902.017,369
Hong Kong (HKG)118.503.337,154
Ashburn (IAD)112.302.017,851
New York (NYC)107.505.217,531
Marseille (MRS)50.701.412,678
Paris (PAR)43.901.272,494
London (LON)42.400.972,508
Amsterdam (AMS)39.301.462,155
Frankfurt (FRA)35.000.652,027
Berlin (BER)27.001.321,613

RTT vs. distance from Moscow

Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent

How to read this chart

Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from Moscow. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).

Underlying measurements
DestinationAvg RTT (ms)Distance (km)
Sydney (SYD)243.6014,484
Melbourne (MEL)236.1014,412
São Paulo (GRU)214.9011,791
Johannesburg (JNB)201.009,126
Los Angeles (LAX)174.309,793
Seattle (SEA)165.208,397
Tokyo (TYO)162.707,497
Singapore (SIN)148.308,423
Miami (MIA)145.109,240
Taipei (TPE)130.907,369
Hong Kong (HKG)118.507,154
Ashburn (IAD)112.307,851
New York (NYC)107.507,531
Marseille (MRS)50.702,678
Paris (PAR)43.902,494
London (LON)42.402,508
Amsterdam (AMS)39.302,155
Frankfurt (FRA)35.002,027
Berlin (BER)27.001,613

Fastest routes into Moscow

Measured RTT from 19 other PoPs into Moscow (MOW), sorted fastest first · each row spans min–max with a dot at the average

How to read this chart

Each row is one 50-probe ICMP echo round from another PoP into Moscow (MOW): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into Moscow can differ from the outbound path shown in the charts above.

Full 19-source dataset
SourceAvg RTT (ms)Min (ms)Max (ms)Distance (km)
Berlin (BER)28.0027.5129.761,613
Frankfurt (FRA)34.8033.1541.232,027
Amsterdam (AMS)38.2036.8143.512,155
London (LON)44.1042.5150.422,508
Paris (PAR)44.5041.6649.772,494
Marseille (MRS)51.3048.7457.192,678
New York (NYC)104.80101.41115.427,531
Ashburn (IAD)113.00108.76126.987,851
Hong Kong (HKG)116.60113.74130.967,154
Taipei (TPE)131.70129.41141.067,369
Miami (MIA)142.20134.33170.689,240
Singapore (SIN)147.60144.71154.688,423
Tokyo (TYO)162.30158.08176.997,497
Seattle (SEA)164.60155.83177.798,397
Los Angeles (LAX)173.70162.94195.199,793
Johannesburg (JNB)200.80196.32215.519,126
São Paulo (GRU)216.20210.33232.8311,791
Melbourne (MEL)235.90229.28265.0014,412
Sydney (SYD)242.30230.31283.8214,484

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 19 other PoPs across 5 continents

Facility & Interconnection

  • Facility: MOW1
  • Upstream transit: RETN / Melbicom
Source
Destination
🇷🇺 Moscow (MOW) → 🇩🇪 Berlin (BER)
27 msExcellent

Latency Summary

MetricValue
Fastest Route🇷🇺 Moscow (MOW) → 🇩🇪 Berlin (BER) (27 ms) — Ultra-Low
Slowest Route🇷🇺 Moscow (MOW) → 🇦🇺 Sydney (SYD) (243.6 ms)
Average RTT126.2 ms
Average Jitter0.97 ms
Average Packet Loss0.05%
Best Fiber Efficiency68.6%
Intra-Region Peers6 PoPs in Europe
Total Routes19 outbound / 19 inbound (100% coverage)

Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.

Geographic & Network Position

Moscow sits on Hats Network's Europe backbone. Measured round-trip times to its 6 intra-region peers range from 27 ms (Berlin (BER)) to 50.7 ms (Marseille (MRS)).

Moscow extends the backbone eastward, providing a transit corridor between European and Asia-Pacific networks.

Outbound Latency from Moscow (MOW)

Round-trip time in milliseconds from Moscow to all other backbone PoPs, sorted fastest to slowest.

DestinationRTT (ms)Fiber FloorEfficiencyJitterLossTier
🇩🇪 Berlin (BER)2715.8 ms58.5%0.26 ms0.11%Ultra-Low
🇩🇪 Frankfurt (FRA)3519.85 ms56.7%0.38 ms0%Excellent
🇳🇱 Amsterdam (AMS)39.321.1 ms53.7%0.28 ms0%Excellent
🇬🇧 London (LON)42.424.56 ms57.9%0.5 ms0%Excellent
🇫🇷 Paris (PAR)43.924.42 ms55.6%0.25 ms0%Excellent
🇫🇷 Marseille (MRS)50.726.23 ms51.7%0.42 ms0.13%Excellent
🇺🇸 New York (NYC)107.573.75 ms68.6%0.9 ms0.16%Good
🇺🇸 Ashburn (IAD)112.376.88 ms68.5%0.6 ms0.03%Good
🇭🇰 Hong Kong (HKG)118.570.05 ms59.1%0.56 ms0.01%Good
🇹🇼 Taipei (TPE)130.972.16 ms55.1%1.52 ms0.11%Good
🇺🇸 Miami (MIA)145.190.48 ms62.4%1 ms0%Good
🇸🇬 Singapore (SIN)148.382.49 ms55.6%0.93 ms0.14%Good
🇯🇵 Tokyo (TYO)162.773.42 ms45.1%1.82 ms0%Fair
🇺🇸 Seattle (SEA)165.282.23 ms49.8%0.92 ms0%Fair
🇺🇸 Los Angeles (LAX)174.395.9 ms55%1.7 ms0%Fair
🇿🇦 Johannesburg (JNB)20189.37 ms44.5%0.93 ms0.05%Fair
🇧🇷 São Paulo (GRU)214.9115.47 ms53.7%2.56 ms0%Fair
🇦🇺 Melbourne (MEL)236.1141.13 ms59.8%1.37 ms0.11%Fair
🇦🇺 Sydney (SYD)243.6141.84 ms58.2%1.56 ms0.1%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.

RankSourceAvg RTTMinMaxStdev
1🇩🇪 Berlin (BER)28 ms27.51 ms29.76 ms0.46 ms
2🇩🇪 Frankfurt (FRA)34.8 ms33.15 ms41.23 ms1.44 ms
3🇳🇱 Amsterdam (AMS)38.2 ms36.81 ms43.51 ms1.46 ms
4🇬🇧 London (LON)44.1 ms42.51 ms50.42 ms1.37 ms
5🇫🇷 Paris (PAR)44.5 ms41.66 ms49.77 ms2.13 ms
6🇫🇷 Marseille (MRS)51.3 ms48.74 ms57.19 ms1.98 ms
7🇺🇸 New York (NYC)104.8 ms101.41 ms115.42 ms2.85 ms
8🇺🇸 Ashburn (IAD)113 ms108.76 ms126.98 ms3.15 ms
9🇭🇰 Hong Kong (HKG)116.6 ms113.74 ms130.96 ms2.93 ms
10🇹🇼 Taipei (TPE)131.7 ms129.41 ms141.06 ms2.24 ms

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.

SourceRTT (ms)Fiber FloorEfficiencyJitterLossTier
🇩🇪 Berlin (BER)2815.8 ms56.4%0.22 ms0.07%Ultra-Low
🇩🇪 Frankfurt (FRA)34.819.85 ms57%0.25 ms0%Excellent
🇳🇱 Amsterdam (AMS)38.221.1 ms55.2%0.26 ms0%Excellent
🇬🇧 London (LON)44.124.56 ms55.7%0.24 ms0.03%Excellent
🇫🇷 Paris (PAR)44.524.42 ms54.9%0.33 ms0.03%Excellent
🇫🇷 Marseille (MRS)51.326.23 ms51.1%0.5 ms0%Excellent
🇺🇸 New York (NYC)104.873.75 ms70.4%0.93 ms0.18%Good
🇺🇸 Ashburn (IAD)11376.88 ms68%0.52 ms0%Good
🇭🇰 Hong Kong (HKG)116.670.05 ms60.1%1.17 ms0.16%Good
🇹🇼 Taipei (TPE)131.772.16 ms54.8%1.06 ms0%Good
🇺🇸 Miami (MIA)142.290.48 ms63.6%1.06 ms0%Good
🇸🇬 Singapore (SIN)147.682.49 ms55.9%1.06 ms0%Good
🇯🇵 Tokyo (TYO)162.373.42 ms45.2%1.1 ms0%Fair
🇺🇸 Seattle (SEA)164.682.23 ms50%0.94 ms0.11%Fair
🇺🇸 Los Angeles (LAX)173.795.9 ms55.2%1.57 ms0.05%Fair
🇿🇦 Johannesburg (JNB)200.889.37 ms44.5%1.94 ms0%Fair
🇧🇷 São Paulo (GRU)216.2115.47 ms53.4%1.52 ms0.01%Fair
🇦🇺 Melbourne (MEL)235.9141.13 ms59.8%1.81 ms0%Fair
🇦🇺 Sydney (SYD)242.3141.84 ms58.5%1.33 ms0.02%Fair

Europe Peers

Moscow is one of 7 Hats Network PoPs in Europe. Intra-region routes offer the lowest latency and highest path diversity.

PoPCodeCountryRTT (ms)Tier
🇳🇱 Amsterdam (AMS)AMSNetherlands39.3Excellent
🇩🇪 Berlin (BER)BERGermany27Ultra-Low
🇩🇪 Frankfurt (FRA)FRAGermany35Excellent
🇬🇧 London (LON)LONUK42.4Excellent
🇫🇷 Marseille (MRS)MRSFrance50.7Excellent
🇫🇷 Paris (PAR)PARFrance43.9Excellent

Frequently Asked Questions

What is the fastest route to Moscow?

The fastest measured route to Moscow (MOW) is Berlin (BER) → Moscow (MOW), averaging 28 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 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 243.6 ms RTT.

Open Data

Measured latency data for Moscow (MOW) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.

🇫🇷 Marseille Ping & Network Latency (MRS) | AS203314

Marseille (MRS) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 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 19 Hats Network (AS203314) backbone PoPs.

On this page

🇷🇺 Moscow (MOW)PoP HighlightsFacility & InterconnectionLatency SummaryGeographic & Network PositionOutbound Latency from Moscow (MOW)Fastest Routes to Moscow (MOW)Inbound Latency to Moscow (MOW)Europe PeersFrequently Asked QuestionsOpen Data