ICMP RTT measurement page for Moscow, Russia to Amsterdam, Netherlands: 50-sample average, jitter, packet loss, minimum and maximum latency.

🇷🇺 Moscow, Russia (MOW) → 🇳🇱 Amsterdam, Netherlands (AMS)

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

In the 2026-08-15T04:03:13Z round, ICMP echo round-trip time from Moscow, Russia to Amsterdam, Netherlands averaged 39.3 ms across 50 samples, with a minimum of 37.75 ms, a maximum of 43.59 ms and zero packet loss.

The route earned an Excellent latency tier rating, with a 1.46 ms standard deviation and 1.15 ms jitter. It ranked 3rd among the 19 paths in its measured set; the median variability across that set was 3.08 percent of average RTT, and this route's relative spread of about 3.7 percent sits just above that typical level even though the absolute variation is small.

The great-circle distance is 2,154.6 km, so the theoretical fiber floor is 21.1 ms; the measured average is 1.86 times that floor, with a fiber efficiency of 53.7 percent. This makes Moscow-Amsterdam a low-latency, efficient path linking Moscow's eastward backbone corridor with Amsterdam's dense Northwest European interconnection ecosystem.

Latency Summary

Metric	Value
RTT	39.3 ms
Jitter	1.15 ms
Packet Loss	0%
Standard Fiber Floor	21.1 ms
Fiber Efficiency	53.7%
Latency Tier	Excellent
Source Region	Europe
Destination Region	Europe

Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

Ping series: MOW → AMS

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 39.3 ± 0.21 ms (SE)

Sample distribution: box = interquartile range (38.1–39.8 ms), median 39.0 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.88
2	100	38.07
3	200	38.23
4	300	38.38
5	400	37.81
6	500	38.01
7	600	37.75
8	700	39.87
9	800	38.46
10	900	40.01
11	1000	38.38
12	1100	39.28
13	1200	39.74
14	1300	38.87
15	1400	39.80
16	1500	40.92
17	1600	42.19
18	1700	39.48
19	1800	38.69
20	1900	39.29
21	2000	42.62
22	2100	43.15
23	2200	39.78
24	2300	38.67
25	2400	39.68
26	2500	40.16
27	2600	39.58
28	2700	38.23
29	2800	37.80
30	2900	43.59
31	3000	39.70
32	3100	40.13
33	3200	42.55
34	3300	39.64
35	3400	38.29
36	3500	37.89
37	3600	37.96
38	3700	37.76
39	3800	37.77
40	3900	38.09
41	4000	41.00
42	4100	40.09
43	4200	38.69
44	4300	38.86
45	4400	39.05
46	4500	39.85
47	4600	39.06
48	4700	38.30
49	4800	37.97
50	4900	37.98

Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See About This Measurement for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Moscow (55.75204, 37.61781) and Amsterdam (52.37403, 4.88969). It does not disclose either facility address.

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.86×

Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full theoretical fiber latency, GeoNames, attenuation, and amplifier methodology.

Stability & Trend

The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	37.75 ms
Average RTT	39.3 ms
Maximum RTT	43.59 ms
Standard deviation	1.46 ms
Stdev / average	3.7%

RTT trend

Estimated route stability across the selected time window.

Average: 39.3 ms
Minimum: 39.0 ms
Maximum: 39.6 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

Reverse direction

Amsterdam to Moscow latency and RTT — 38.2 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27 ms
Moscow to Frankfurt latency and RTT — 35 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 43.9 ms
Moscow to Marseille latency and RTT — 50.7 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.6 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

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data 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}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Amsterdam round 2026-08-15T04:03:13Z, CC BY 4.0".

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Moscow, Russia → Amsterdam, Netherlands RTT