# Berlin, Germany → Melbourne, Australia RTT

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

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

During round 2026-08-16T04:07:28Z, 50 ICMP echo samples from Berlin, Germany to Melbourne, Australia averaged 256.2 ms, with a minimum of 246.67 ms, a maximum of 285.1 ms, and zero packet loss. Jitter of 5.78 ms and a standard deviation of 7.82 ms place this route in the high latency tier.

Relative to the 156.34 ms fiber floor for the 15,965 km geodesic, the measured average is 1.64 times that floor, or 61% fiber efficiency. The route's variability is about 3.05% of the average, just below the 3.28% median variability across the 19 routes in this round.

Ranked 18th of those 19, this is a high-latency route, but it is not an erratic one: zero packet loss and a jitter below 6 ms keep the connection consistent despite the long distance. Its fiber efficiency is reasonably good for a path of this length, meaning the extra milliseconds are largely explained by geography.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **256.2 ms**                                               |
| Jitter               | **5.78 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **156.34 ms**                                              |
| Fiber Efficiency     | **61%**                                                    |
| Latency Tier         | High                                                       |
| Source Region        | [Europe](/docs/network/latency/regions/europe)             |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332). 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](/docs/network/latency/theoretical-fiber-latency).

## 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        | **246.67 ms** |
| Average RTT        | **256.2 ms**  |
| Maximum RTT        | **285.1 ms**  |
| Standard deviation | **7.82 ms**   |
| Stdev / average    | **3.1%**      |

## Route Context

* Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Melbourne to Berlin latency and RTT](/docs/network/latency/pairs/mel-ber-rtt) — 254.7 ms

**Fastest routes departing Berlin (BER)**

* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms
* [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms

**Fastest routes arriving at Melbourne (MEL)**

* [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms
* [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms
* [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 ms
* [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms
* [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 ms

**Same corridor (Europe → Asia Pacific)**

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ber-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Melbourne round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ber-mel-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.