ICMP RTT data for Melbourne, Australia to Berlin, Germany: average 254.7 ms, zero packet loss, jitter and 2026-08-16 route stability.

🇦🇺 Melbourne, Australia (MEL) → 🇩🇪 Berlin, Germany (BER)

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

In the measurement round 2026-08-16T04:07:28Z, the Melbourne-to-Berlin path returned an average ICMP echo RTT of 254.7 ms, with a minimum of 239.97 ms and a maximum of 301.16 ms. None of the 50 probes were lost, and the standard deviation was 11.1 ms (jitter 10.6 ms), so the intercontinental path was stable despite its high latency tier.

The average is 1.63 times the theoretical fiber floor for the 15,965.1 km great-circle distance, which translates to 61.4% fiber-floor efficiency. Within the 19 outbound route options in this measurement set, this path ranks 17th by outbound latency; the peer group's median standard-deviation-to-average ratio is 3.28%, helping to contextualize the observed spread.

The zero packet loss and narrow 61.19 ms gap between minimum and maximum indicate that this direction had healthy capacity at test time. Because the minimum sits only about 14.7 ms below the average, the route's steady-state latency is close to its best observed case, so the numbers from this round can serve as a baseline for future Melbourne–Berlin troubleshooting.

Latency Summary

Metric	Value
RTT	254.7 ms
Jitter	10.6 ms
Packet Loss	0%
Standard Fiber Floor	156.34 ms
Fiber Efficiency	61.4%
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 → BER

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 254.7 ± 1.57 ms (SE)

Sample distribution: box = interquartile range (246.2–260.2 ms), median 252.6 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 (156.3 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	265.00
2	100	250.50
3	200	258.18
4	300	244.94
5	400	258.09
6	500	253.95
7	600	243.98
8	700	263.43
9	800	253.74
10	900	262.57
11	1000	258.54
12	1100	250.98
13	1200	263.49
14	1300	261.75
15	1400	249.38
16	1500	248.98
17	1600	241.67
18	1700	239.97
19	1800	245.87
20	1900	301.16
21	2000	260.87
22	2100	261.33
23	2200	249.33
24	2300	242.80
25	2400	260.20
26	2500	260.10
27	2600	249.87
28	2700	249.61
29	2800	256.55
30	2900	244.56
31	3000	252.27
32	3100	246.10
33	3200	262.29
34	3300	251.37
35	3400	250.93
36	3500	248.66
37	3600	244.92
38	3700	244.42
39	3800	254.26
40	3900	269.78
41	4000	252.88
42	4100	243.88
43	4200	243.81
44	4300	258.84
45	4400	246.46
46	4500	244.63
47	4600	255.18
48	4700	287.80
49	4800	269.19
50	4900	255.94

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

Physical Reference	Value
WGS-84 geodesic distance	15,965.1 km
Vacuum RTT floor	106.51 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	156.34 ms
Low-latency fiber material floor	155.71 ms
Engineering floor (5% path allowance)	164.18 ms
Research 1.33× mapped-fiber reference	207.94 ms
Estimated unamplified path loss	3352.7 dB
Transparent optical spans / inline amplifiers	210 / 209
Published RTT inflation over fiber floor	1.63×

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	239.97 ms
Average RTT	254.7 ms
Maximum RTT	301.16 ms
Standard deviation	11.1 ms
Stdev / average	4.4%

RTT trend

Estimated route stability across the selected time window.

Average: 254.7 ms
Minimum: 252.2 ms
Maximum: 256.9 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Berlin to Melbourne latency and RTT — 256.2 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 Berlin (BER)

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