ICMP RTT measurement from Melbourne to Amsterdam, Netherlands: average latency, jitter, packet loss, and route efficiency for the Australia–Netherlands path.

🇦🇺 Melbourne, Australia (MEL) → 🇳🇱 Amsterdam, Netherlands (AMS)

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

For the 2026-08-15T04:03:13Z round, 50 ICMP samples from Melbourne to Amsterdam averaged 252.5 ms, with a 7.97 ms standard deviation and zero packet loss. The minimum of 243.54 ms and maximum of 283.04 ms, plus 5.81 ms jitter, put the route in the High latency tier, as expected for a transcontinental path.

The straight-line fiber floor for the 16,540.5 km separation is 161.98 ms; the measured 252.5 ms is 1.56 times that floor, giving 64.1% fiber efficiency. That is a comparatively tight overhead for such a long route, and it suggests the observed latency is dominated by distance rather than by path inefficiency.

This path placed 15th out of 19 outbound routes measured from Melbourne, so it is not one of the faster options in the set. Its relative variability, approximately 3.2%, is close to the 3.08% median relative variability across the comparable routes, meaning the route stays steady even though average latency is high.

Latency Summary

Metric	Value
RTT	252.5 ms
Jitter	5.81 ms
Packet Loss	0%
Standard Fiber Floor	161.98 ms
Fiber Efficiency	64.1%
Latency Tier	High
Source Region	Asia Pacific
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: MEL → AMS

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

Sample distribution: box = interquartile range (247.3–254.8 ms), median 250.3 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 (162.0 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	243.54
2	100	243.68
3	200	244.25
4	300	247.13
5	400	249.09
6	500	246.08
7	600	254.97
8	700	247.67
9	800	246.00
10	900	245.80
11	1000	250.03
12	1100	247.06
13	1200	252.05
14	1300	248.40
15	1400	254.21
16	1500	247.61
17	1600	252.34
18	1700	253.54
19	1800	257.79
20	1900	248.34
21	2000	260.80
22	2100	260.68
23	2200	251.20
24	2300	283.04
25	2400	279.08
26	2500	259.82
27	2600	250.37
28	2700	248.17
29	2800	252.21
30	2900	246.93
31	3000	255.37
32	3100	260.63
33	3200	250.30
34	3300	247.49
35	3400	251.70
36	3500	246.23
37	3600	246.37
38	3700	259.46
39	3800	250.74
40	3900	251.07
41	4000	246.61
42	4100	250.66
43	4200	250.03
44	4300	250.12
45	4400	266.96
46	4500	260.27
47	4600	264.02
48	4700	250.36
49	4800	247.56
50	4900	247.17

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 Melbourne (-37.81400, 144.96332) and Amsterdam (52.37403, 4.88969). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	16,540.5 km
Vacuum RTT floor	110.35 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	161.98 ms
Low-latency fiber material floor	161.33 ms
Engineering floor (5% path allowance)	170.1 ms
Research 1.33× mapped-fiber reference	215.43 ms
Estimated unamplified path loss	3473.5 dB
Transparent optical spans / inline amplifiers	218 / 217
Published RTT inflation over fiber floor	1.56×

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	243.54 ms
Average RTT	252.5 ms
Maximum RTT	283.04 ms
Standard deviation	7.97 ms
Stdev / average	3.2%

RTT trend

Estimated route stability across the selected time window.

Average: 252.9 ms
Minimum: 250.6 ms
Maximum: 255.3 ms
Average loss: 0.02%

Route Context

Departure PoP: Melbourne (MEL)
Destination PoP: Amsterdam (AMS)
Region overview: Asia Pacific → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Amsterdam to Melbourne latency and RTT — 254.2 ms

Fastest routes departing Melbourne (MEL)

Melbourne to Sydney latency and RTT — 9.8 ms
Melbourne to Singapore latency and RTT — 88.3 ms
Melbourne to Tokyo latency and RTT — 113.2 ms
Melbourne to Hong Kong latency and RTT — 137.4 ms
Melbourne to Taipei latency and RTT — 141.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 (Asia Pacific → Europe)

Hong Kong to Moscow latency and RTT — 116.6 ms
Taipei to Moscow latency and RTT — 131.7 ms
Singapore to Marseille latency and RTT — 138.8 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/mel-ams.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → 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.

Melbourne, Australia → Amsterdam, Netherlands RTT