ICMP RTT measurements from Amsterdam, Netherlands to Moscow, Russia: average latency, minimum, maximum, jitter, packet loss, and route efficiency.

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

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

ICMP echo probes for the 2026-08-15T04:03:13Z round from Amsterdam, Netherlands to Moscow, Russia averaged 38.2 ms RTT over 50 samples, with a minimum of 36.81 ms and a maximum of 43.51 ms. The route lost no packets and kept jitter at 1.04 ms.

At 1.46 ms, the standard deviation is about 3.8% of the average, slightly above the 3.08% median variability observed across the outbound measurement set. The route ranks sixth among the 19 outbound paths in this round.

Given the 2,154.6 km geodesic distance, the fiber-floor estimate is 21.1 ms; the measured average is 1.81 times that floor, so fiber efficiency is about 55.2%. The extra time over the straight-line estimate is reasonable for a long continental path and still classifies the connection as excellent for ICMP RTT.

Latency Summary

Metric	Value
RTT	38.2 ms
Jitter	1.04 ms
Packet Loss	0%
Standard Fiber Floor	21.1 ms
Fiber Efficiency	55.2%
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: AMS → MOW

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

Sample distribution: box = interquartile range (37.2–38.5 ms), median 37.8 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.81
2	100	37.48
3	200	37.43
4	300	36.97
5	400	38.33
6	500	40.81
7	600	38.55
8	700	43.51
9	800	39.68
10	900	38.42
11	1000	37.98
12	1100	37.97
13	1200	37.92
14	1300	37.81
15	1400	38.73
16	1500	41.44
17	1600	39.73
18	1700	38.54
19	1800	37.34
20	1900	36.92
21	2000	36.96
22	2100	37.15
23	2200	37.10
24	2300	36.81
25	2400	37.55
26	2500	37.42
27	2600	37.00
28	2700	36.82
29	2800	36.86
30	2900	36.82
31	3000	36.87
32	3100	37.38
33	3200	37.15
34	3300	38.47
35	3400	42.27
36	3500	39.49
37	3600	39.26
38	3700	38.49
39	3800	37.53
40	3900	37.03
41	4000	38.10
42	4100	40.91
43	4200	38.41
44	4300	37.59
45	4400	37.81
46	4500	39.61
47	4600	37.76
48	4700	37.30
49	4800	37.49
50	4900	37.22

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 Amsterdam (52.37403, 4.88969) and Moscow (55.75204, 37.61781). 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.81×

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	36.81 ms
Average RTT	38.2 ms
Maximum RTT	43.51 ms
Standard deviation	1.46 ms
Stdev / average	3.8%

RTT trend

Estimated route stability across the selected time window.

Average: 38.2 ms
Minimum: 37.8 ms
Maximum: 38.6 ms
Average loss: 0.03%

Route Context

Departure PoP: Amsterdam (AMS)
Destination PoP: Moscow (MOW)
Region overview: Europe → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Moscow to Amsterdam latency and RTT — 39.3 ms

Fastest routes departing Amsterdam (AMS)

Amsterdam to London latency and RTT — 5.1 ms
Amsterdam to Frankfurt latency and RTT — 5.9 ms
Amsterdam to Paris latency and RTT — 7 ms
Amsterdam to Berlin latency and RTT — 7.2 ms
Amsterdam to Marseille latency and RTT — 19.7 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28 ms
Frankfurt to Moscow latency and RTT — 34.8 ms
London to Moscow latency and RTT — 44.1 ms
Paris to Moscow latency and RTT — 44.5 ms
Marseille to Moscow latency and RTT — 51.3 ms

Same corridor (Europe → Europe)

London to Amsterdam latency and RTT — 5.1 ms
Frankfurt to Amsterdam 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/ams-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Moscow 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.

Amsterdam, Netherlands → Moscow, Russia RTT