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-08-16T04:07:28Z.

Moscow to Amsterdam averaged 37.6 ms across 50 replies. The observed range was 37.09 to 39.9 ms; these figures describe one probe round, not a long-term service target.

This is number 3 of 19 outgoing routes by average RTT. That ranking compares different destinations and is not adjusted for distance.

Latency Summary

Metric	Value
RTT	37.6 ms
Jitter	0.36 ms
Packet Loss	0%
Standard Fiber Floor	21.1 ms
Fiber Efficiency	56.1%
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-08-16T04:07:28Z · avg 37.6 ± 0.08 ms (SE)

Sample distribution: box = interquartile range (37.2–37.7 ms), median 37.4 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	39.52
2	100	37.91
3	200	37.93
4	300	37.47
5	400	37.90
6	500	37.36
7	600	37.29
8	700	37.62
9	800	37.39
10	900	37.17
11	1000	37.32
12	1100	37.13
13	1200	37.26
14	1300	37.24
15	1400	37.55
16	1500	37.21
17	1600	37.11
18	1700	37.22
19	1800	37.55
20	1900	37.62
21	2000	38.95
22	2100	39.90
23	2200	38.40
24	2300	38.00
25	2400	37.92
26	2500	37.35
27	2600	37.11
28	2700	37.25
29	2800	37.32
30	2900	37.62
31	3000	37.32
32	3100	37.70
33	3200	37.40
34	3300	37.67
35	3400	37.23
36	3500	37.72
37	3600	37.95
38	3700	37.94
39	3800	37.36
40	3900	37.22
41	4000	37.31
42	4100	38.33
43	4200	37.49
44	4300	37.17
45	4400	37.47
46	4500	37.45
47	4600	37.22
48	4700	37.13
49	4800	37.24
50	4900	37.09

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.

CSV JSON YAML Full dataset

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 ( $n_g=1.4679$ )	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.78×

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.09 ms
Average RTT	37.6 ms
Maximum RTT	39.9 ms
Standard deviation	0.57 ms
Stdev / average	1.5%

Estimated RTT trend

Modeled comparison, not historical probe measurements.

Average: 37.6 ms
Minimum: 37.3 ms
Maximum: 37.9 ms
Average loss: 0.03%

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

Reverse direction

Amsterdam to Moscow latency and RTT: 38.1 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT: 27.5 ms
Moscow to Frankfurt latency and RTT: 35.9 ms
Moscow to London latency and RTT: 42.4 ms
Moscow to Paris latency and RTT: 44 ms
Moscow to Marseille latency and RTT: 49.9 ms

Fastest routes arriving at Amsterdam (AMS)

London to Amsterdam latency and RTT: 5.2 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: 20.3 ms

Same corridor (Europe → Europe)

Amsterdam to London latency and RTT: 5.2 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-08-16T04:07:28Z, CC BY 4.0".

Round published August 16, 2026. See the full interactive latency matrix or browse more city-pair routes.

Moscow, Russia → Amsterdam, Netherlands RTT