Measured ICMP echo RTT from Melbourne, Australia to Amsterdam, Netherlands: 252.8 ms average, 0% loss, high latency tier in round 2026-08-16T04:07:28Z.

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

Measurement round: 2026-08-16T04:07:28Z.

Round 2026-08-16T04:07:28Z measured ICMP echo RTT between Melbourne and Amsterdam at an average of 252.8 ms, with a 241.73 ms minimum, a 276.97 ms maximum, and zero packet loss across 50 samples. The 7.18 ms standard deviation and 6.4 ms jitter are modest for a 16,540.5 km intercontinental route, and the high latency tier is consistent with the distance.

This path ranks 16th out of the 19 outbound routes in this round, placing it toward the high-latency end of the measured set. Its variability ratio of about 2.8% is below the 3.28% network-wide median, so relative to its delay the route is actually quite consistent.

The observed RTT is 1.56 times the 161.98 ms fiber floor for the great-circle distance, a fiber efficiency of 64.1%. Most of the delay is the unavoidable distance, while the 0% loss and low jitter suggest a clean transcontinental path during the measurement window.

Latency Summary

Metric	Value
RTT	252.8 ms
Jitter	6.4 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-16T04:07:28Z · avg 252.8 ± 1.02 ms (SE)

Sample distribution: box = interquartile range (248.1–256.2 ms), median 251.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	252.80
2	100	251.38
3	200	251.46
4	300	245.38
5	400	242.73
6	500	241.73
7	600	255.17
8	700	252.77
9	800	248.28
10	900	247.68
11	1000	253.24
12	1100	252.81
13	1200	258.06
14	1300	251.71
15	1400	257.83
16	1500	247.40
17	1600	254.51
18	1700	249.10
19	1800	244.24
20	1900	258.68
21	2000	251.27
22	2100	249.84
23	2200	248.39
24	2300	246.37
25	2400	255.05
26	2500	256.59
27	2600	248.27
28	2700	250.98
29	2800	245.00
30	2900	253.22
31	3000	272.67
32	3100	268.06
33	3200	257.44
34	3300	248.02
35	3400	248.77
36	3500	276.97
37	3600	260.97
38	3700	251.14
39	3800	252.69
40	3900	250.36
41	4000	247.28
42	4100	268.37
43	4200	258.60
44	4300	248.82
45	4400	246.23
46	4500	248.01
47	4600	245.68
48	4700	251.17
49	4800	256.57
50	4900	260.24

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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	241.73 ms
Average RTT	252.8 ms
Maximum RTT	276.97 ms
Standard deviation	7.18 ms
Stdev / average	2.8%

RTT trend

Estimated route stability across the selected time window.

Average: 252.7 ms
Minimum: 250.1 ms
Maximum: 254.7 ms
Average loss: 0.00%

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 — 252.5 ms

Fastest routes departing Melbourne (MEL)

Melbourne to Sydney latency and RTT — 9.8 ms
Melbourne to Singapore latency and RTT — 88.4 ms
Melbourne to Tokyo latency and RTT — 112 ms
Melbourne to Hong Kong latency and RTT — 138.5 ms
Melbourne to Taipei latency and RTT — 143.2 ms

Fastest routes arriving at Amsterdam (AMS)

London to Amsterdam latency and RTT — 5.2 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 — 20.3 ms

Same corridor (Asia Pacific → Europe)

Hong Kong to Moscow latency and RTT — 118.2 ms
Taipei to Moscow latency and RTT — 132.7 ms
Singapore to Marseille latency and RTT — 140.6 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-16T04:07:28Z, CC BY 4.0".

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

Melbourne, Australia → Amsterdam, Netherlands RTT