ICMP RTT measurement results for Amsterdam, Netherlands to Berlin, Germany, including average latency, jitter, packet loss, and route stability.

🇳🇱 Amsterdam, Netherlands (AMS) → 🇩🇪 Berlin, Germany (BER)

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

During the 2026-08-15T04:03:13Z measurement round, ICMP echo requests from Amsterdam to Berlin returned an average round-trip time of 7.2 ms, with a minimum of 6.92 ms, a maximum of 7.88 ms, and zero packet loss. Standard deviation was 0.21 ms and jitter 0.15 ms, so the route remained highly consistent across all 50 samples.

At 579 km, the direct distance implies a fiber-floor latency of 5.67 ms; the observed 7.2 ms RTT is 1.27 times that floor, corresponding to a fiber efficiency of 78.8 percent. That leaves a relatively small gap to the physical minimum, indicating that the extra latency above the theoretical minimum is modest.

Among the 19 outbound routes measured from Amsterdam in this window, this pairing ranked 4th by average RTT, while the network-wide median variability was 3.08 percent. The route's own standard deviation of 0.21 ms works out to roughly 2.9 percent of the average, slightly tighter than that median, so the average RTT is a dependable descriptor for this ICMP path.

Latency Summary

Metric	Value
RTT	7.2 ms
Jitter	0.15 ms
Packet Loss	0%
Standard Fiber Floor	5.67 ms
Fiber Efficiency	78.8%
Latency Tier	Ultra-Low
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 → BER

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

Sample distribution: box = interquartile range (7.0–7.3 ms), median 7.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 (5.7 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	6.98
2	100	7.07
3	200	7.07
4	300	7.00
5	400	6.96
6	500	6.92
7	600	7.03
8	700	6.97
9	800	7.43
10	900	7.38
11	1000	7.67
12	1100	7.88
13	1200	7.31
14	1300	7.29
15	1400	7.76
16	1500	7.40
17	1600	7.23
18	1700	7.31
19	1800	7.29
20	1900	7.34
21	2000	7.15
22	2100	7.05
23	2200	7.24
24	2300	7.43
25	2400	7.27
26	2500	7.13
27	2600	7.08
28	2700	7.07
29	2800	7.46
30	2900	7.36
31	3000	7.37
32	3100	7.27
33	3200	7.04
34	3300	7.00
35	3400	7.28
36	3500	7.04
37	3600	6.97
38	3700	6.95
39	3800	6.92
40	3900	6.99
41	4000	7.37
42	4100	7.07
43	4200	7.06
44	4300	7.27
45	4400	7.22
46	4500	7.13
47	4600	7.01
48	4700	7.29
49	4800	7.10
50	4900	7.12

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 Berlin (52.52437, 13.41053). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	579.2 km
Vacuum RTT floor	3.86 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	5.67 ms
Low-latency fiber material floor	5.65 ms
Engineering floor (5% path allowance)	5.96 ms
Research 1.33× mapped-fiber reference	7.54 ms
Estimated unamplified path loss	121.6 dB
Transparent optical spans / inline amplifiers	8 / 7
Published RTT inflation over fiber floor	1.27×

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	6.92 ms
Average RTT	7.2 ms
Maximum RTT	7.88 ms
Standard deviation	0.21 ms
Stdev / average	2.9%

RTT trend

Estimated route stability across the selected time window.

Average: 7.2 ms
Minimum: 7.1 ms
Maximum: 7.3 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Berlin to Amsterdam latency and RTT — 7.2 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 Marseille latency and RTT — 19.7 ms
Amsterdam to Moscow latency and RTT — 38.2 ms

Fastest routes arriving at Berlin (BER)

Frankfurt to Berlin latency and RTT — 6.1 ms
Paris to Berlin latency and RTT — 14.8 ms
London to Berlin latency and RTT — 16.2 ms
Marseille to Berlin latency and RTT — 21.5 ms
Moscow to Berlin latency and RTT — 27 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-ber.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Berlin 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 → Berlin, Germany RTT