ICMP round-trip time from Amsterdam, Netherlands, to Melbourne, Australia: 50 samples, 254.2 ms average, 0% loss, and route latency context.

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

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

In the 2026-08-15T04:03:13Z round, ICMP echo RTT from Amsterdam to Melbourne averaged 254.2 ms over 50 samples at 100 ms intervals, with a minimum of 243.41 ms, a maximum of 279.26 ms, and a standard deviation of 9.34 ms. No packets were lost, so the route was reachable for the full measurement window.

Ranked 18th among the 19 outbound routes measured from Amsterdam in that round, this is near the slow end of the set. Its variability-to-average ratio of about 3.7% sits slightly above the 3.08% median across those routes, so the high base latency is accompanied by a little more spread than the typical Amsterdam outbound path.

The observed average is 1.57 times the straight-line fiber floor of 161.98 ms, for a fiber efficiency of 63.7%. The 35.85 ms difference between minimum and maximum replies and 7.91 ms jitter mean the path can add tens of milliseconds on top of an already long round trip, which is worth weighing for time-sensitive traffic even though ICMP RTT does not measure end-user application experience.

Latency Summary

Metric	Value
RTT	254.2 ms
Jitter	7.91 ms
Packet Loss	0%
Standard Fiber Floor	161.98 ms
Fiber Efficiency	63.7%
Latency Tier	High
Source Region	Europe
Destination Region	Asia Pacific

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 → MEL

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

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

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	247.63
2	100	245.45
3	200	256.59
4	300	251.31
5	400	246.74
6	500	244.75
7	600	244.54
8	700	246.87
9	800	260.05
10	900	249.05
11	1000	251.53
12	1100	246.04
13	1200	246.51
14	1300	256.53
15	1400	255.95
16	1500	254.81
17	1600	252.13
18	1700	276.48
19	1800	258.06
20	1900	249.33
21	2000	244.01
22	2100	255.37
23	2200	250.38
24	2300	273.99
25	2400	272.76
26	2500	279.26
27	2600	255.84
28	2700	247.27
29	2800	243.61
30	2900	254.75
31	3000	268.67
32	3100	255.69
33	3200	248.42
34	3300	243.74
35	3400	255.73
36	3500	259.84
37	3600	257.78
38	3700	249.34
39	3800	271.65
40	3900	259.24
41	4000	247.83
42	4100	253.70
43	4200	254.58
44	4300	267.53
45	4400	268.45
46	4500	251.04
47	4600	244.63
48	4700	246.88
49	4800	244.26
50	4900	243.41

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 Melbourne (-37.81400, 144.96332). 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.57×

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.41 ms
Average RTT	254.2 ms
Maximum RTT	279.26 ms
Standard deviation	9.34 ms
Stdev / average	3.7%

RTT trend

Estimated route stability across the selected time window.

Average: 254.5 ms
Minimum: 252.0 ms
Maximum: 256.9 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Melbourne to Amsterdam latency and RTT — 252.5 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 Melbourne (MEL)

Sydney to Melbourne latency and RTT — 9.8 ms
Singapore to Melbourne latency and RTT — 87.8 ms
Tokyo to Melbourne latency and RTT — 111.3 ms
Hong Kong to Melbourne latency and RTT — 137.4 ms
Taipei to Melbourne latency and RTT — 143.6 ms

Same corridor (Europe → Asia Pacific)

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