Measured ICMP RTT between Melbourne, Australia and Berlin, Germany: average latency, jitter, packet loss, and fiber-floor efficiency for this long-haul route.

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

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

During the 2026-08-15T04:03:13Z measurement round, ICMP echo RTT from Melbourne to Berlin averaged 256.6 ms across 50 samples, with a minimum of 248.2 ms and a maximum of 280.3 ms. The route recorded zero packet loss and jitter of 6.51 ms.

The 15,965.1 km geodesic distance gives a theoretical vacuum floor of 106.51 ms and a fiber floor of 156.34 ms. The observed average is 1.64 times the fiber floor, translating to 60.9% fiber efficiency and indicating the expected headroom for an intercontinental path.

On the 19 outbound routes measured from this source, this route ranked 16th by average latency. Its standard deviation of 7.86 ms is 3.06% of the average, slightly below the 3.08% network-wide median for standard deviation as a share of average.

With no packet loss and a tight spread around the mean, the path was stable over the sampling window; the 1.64x inflation over the fiber floor offers a useful baseline for comparing future measurements on this route.

Latency Summary

Metric	Value
RTT	256.6 ms
Jitter	6.51 ms
Packet Loss	0%
Standard Fiber Floor	156.34 ms
Fiber Efficiency	60.9%
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-15T04:03:13Z · avg 256.6 ± 1.11 ms (SE)

Sample distribution: box = interquartile range (250.3–260.3 ms), median 253.5 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	250.05
2	100	270.52
3	200	257.67
4	300	252.40
5	400	256.54
6	500	273.25
7	600	265.00
8	700	253.50
9	800	252.86
10	900	250.50
11	1000	255.13
12	1100	252.27
13	1200	259.48
14	1300	260.65
15	1400	271.56
16	1500	255.96
17	1600	253.96
18	1700	249.50
19	1800	250.19
20	1900	248.74
21	2000	273.41
22	2100	258.88
23	2200	260.62
24	2300	257.64
25	2400	250.84
26	2500	248.77
27	2600	251.24
28	2700	252.41
29	2800	263.82
30	2900	253.07
31	3000	249.74
32	3100	253.52
33	3200	266.12
34	3300	258.15
35	3400	251.45
36	3500	260.68
37	3600	257.74
38	3700	263.27
39	3800	280.30
40	3900	272.23
41	4000	258.86
42	4100	251.43
43	4200	251.42
44	4300	248.81
45	4400	250.08
46	4500	249.36
47	4600	249.95
48	4700	248.20
49	4800	249.62
50	4900	248.64

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.64×

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	248.2 ms
Average RTT	256.6 ms
Maximum RTT	280.3 ms
Standard deviation	7.86 ms
Stdev / average	3.1%

RTT trend

Estimated route stability across the selected time window.

Average: 256.3 ms
Minimum: 254.1 ms
Maximum: 258.2 ms
Average loss: 0.03%

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 — 255.8 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 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 — 14.8 ms
London to Berlin latency and RTT — 16.2 ms
Marseille to Berlin latency and RTT — 21.5 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-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-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 → Berlin, Germany RTT