Moscow, Russia → Amsterdam, Netherlands RTT
Explore Moscow, Russia to Amsterdam, Netherlands ICMP RTT, jitter, packet loss and fiber latency limits on the AS203314 network.
🇷🇺 Moscow, Russia (MOW) → 🇳🇱 Amsterdam, Netherlands (AMS)
Measurement round: 2026-10-20T08:46:17Z.
Moscow–Amsterdam averaged 39.5 ms, with RTTs ranging from 37.45 to 44.44 ms and zero measured packet loss.
The average is about 1.87 times the fiber reference. Third place among 19 outbound routes places Amsterdam among Moscow's fastest measured destinations.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 39.5 ms |
| Jitter | 1.47 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 21.1 ms |
| Fiber Efficiency | 53.4% |
| Latency Tier | Excellent |
| Source Region | Europe |
| Destination Region | Europe |
Ping Measurement Series
50 ICMP echo probes were recorded in this round. Individual replies and their distribution are shown below.
Ping series: MOW → AMS
50 ICMP echo samples at 100 ms intervals · round 2026-10-20T08:46:17Z · avg 39.5 ± 0.23 ms (SE)
Sample distribution: box = interquartile range (38.3–40.0 ms), median 39.1 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly. The band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (21.1 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 37.45 |
| 2 | 100 | 39.75 |
| 3 | 200 | 40.37 |
| 4 | 300 | 42.50 |
| 5 | 400 | 41.82 |
| 6 | 500 | 39.93 |
| 7 | 600 | 38.90 |
| 8 | 700 | 44.44 |
| 9 | 800 | 41.03 |
| 10 | 900 | 39.77 |
| 11 | 1000 | 38.31 |
| 12 | 1100 | 38.42 |
| 13 | 1200 | 38.06 |
| 14 | 1300 | 38.37 |
| 15 | 1400 | 43.73 |
| 16 | 1500 | 42.19 |
| 17 | 1600 | 39.05 |
| 18 | 1700 | 39.31 |
| 19 | 1800 | 38.24 |
| 20 | 1900 | 37.72 |
| 21 | 2000 | 41.84 |
| 22 | 2100 | 39.14 |
| 23 | 2200 | 38.08 |
| 24 | 2300 | 38.24 |
| 25 | 2400 | 37.95 |
| 26 | 2500 | 37.91 |
| 27 | 2600 | 38.54 |
| 28 | 2700 | 39.78 |
| 29 | 2800 | 38.87 |
| 30 | 2900 | 40.57 |
| 31 | 3000 | 40.07 |
| 32 | 3100 | 39.83 |
| 33 | 3200 | 38.73 |
| 34 | 3300 | 40.61 |
| 35 | 3400 | 38.52 |
| 36 | 3500 | 39.19 |
| 37 | 3600 | 43.48 |
| 38 | 3700 | 39.59 |
| 39 | 3800 | 38.45 |
| 40 | 3900 | 37.72 |
| 41 | 4000 | 37.65 |
| 42 | 4100 | 39.05 |
| 43 | 4200 | 38.90 |
| 44 | 4300 | 37.90 |
| 45 | 4400 | 39.25 |
| 46 | 4500 | 40.78 |
| 47 | 4600 | 39.36 |
| 48 | 4700 | 38.31 |
| 49 | 4800 | 38.00 |
| 50 | 4900 | 39.33 |
Download This Route's Data
Download the probe round as CSV, JSON or YAML under CC BY 4.0. Citation details include the route and round timestamp.
Theoretical Fiber Latency
The propagation model uses public city-centre coordinates from GeoNames: Moscow (55.75204, 37.61781) and Amsterdam (52.37403, 4.88969). These are not facility coordinates or a surveyed cable path.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 2,154.6 km |
| Vacuum RTT floor | 14.37 ms |
| Standard fiber RTT floor () | 21.1 ms |
| Low-latency fiber material floor | 21.02 ms |
| Engineering floor (5% path allowance) | 22.16 ms |
| Research 1.33× mapped-fiber reference | 28.06 ms |
| Estimated unamplified path loss | 452.5 dB |
| Transparent optical spans / inline amplifiers | 29 / 28 |
| Published RTT inflation over fiber floor | 1.87× |
The span count assumes 80 km optical spans. Attenuation is a power-loss term, not a propagation delay. See the model assumptions and equations.
Stability & Trend
Statistics from the same 50 replies. They describe this probe round, not continuous historical monitoring.
| Round Statistic | Value |
|---|---|
| Minimum RTT | 37.45 ms |
| Average RTT | 39.5 ms |
| Maximum RTT | 44.44 ms |
| Standard deviation | 1.64 ms |
| Stdev / average | 4.2% |
Estimated RTT trend
Modeled comparison, not historical probe measurements.
- Average
- 39.5 ms
- Minimum
- 39.1 ms
- Maximum
- 39.9 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Moscow (MOW)
- Destination PoP: Amsterdam (AMS)
- Region overview: Europe → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Amsterdam to Moscow latency and RTT: 40.1 ms
Fastest routes departing Moscow (MOW)
- Moscow to Berlin latency and RTT: 28.3 ms
- Moscow to Frankfurt latency and RTT: 36.3 ms
- Moscow to London latency and RTT: 43.7 ms
- Moscow to Paris latency and RTT: 45.3 ms
- Moscow to Marseille latency and RTT: 51.5 ms
Fastest routes arriving at Amsterdam (AMS)
- London to Amsterdam latency and RTT: 5.1 ms
- Frankfurt to Amsterdam latency and RTT: 5.9 ms
- Paris to Amsterdam latency and RTT: 7 ms
- Berlin to Amsterdam latency and RTT: 7.2 ms
- Marseille to Amsterdam latency and RTT: 19.2 ms
Same corridor (Europe → Europe)
- Amsterdam to London latency and RTT: 5.1 ms
- Amsterdam to Frankfurt latency and RTT: 5.9 ms
- Berlin to Frankfurt latency and RTT: 6.1 ms
About This Measurement
These ICMP measurements cover the two backbone endpoints. Access networks, routing policy and load can change an end user's result. A probe round is not an SLA.
The underlying replies are available under CC BY 4.0 in the Hats Network latency dataset. Per-pair files are available at /opendata/latency/latest/pairs/mow-ams.pings.{csv,json,yaml}. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Moscow → Amsterdam round 2026-10-20T08:46:17Z, CC BY 4.0".
Round published October 20, 2026. See the full interactive latency matrix or browse more city-pair routes.