# Melbourne, Australia → Hong Kong RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇭🇰 **Hong Kong (HKG)**

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

During the 2026-08-16T04:07:28Z ICMP echo round, 50 probes at 100 ms intervals from Melbourne, Australia to Hong Kong returned an average RTT of 138.5 ms, with a minimum of 133.73 ms and a maximum of 150.99 ms. No packets were lost, and jitter was 3.66 ms, indicating a stable long-haul path.

Relative to the 72.38 ms fibre-floor estimate for the 7,391 km geodesic separation, the measured average is 1.91 times that ideal, or roughly 91% above the physical minimum. The 4.36 ms standard deviation is consistent with the 133.73–150.99 ms range, and the route's 52.3% fibre efficiency leaves a clear gap to the theoretical optimum.

In the 19-route outbound set from this Melbourne source, the Hong Kong path is ranked fourth. Its standard deviation as a share of the average is about 3.15%, slightly tighter than the 3.28% median relative spread for the set, and the zero-loss sample reinforces that the RTT distribution is compact for a route covering more than 7,000 km.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **138.5 ms**                                               |
| Jitter               | **3.66 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **72.38 ms**                                               |
| Fiber Efficiency     | **52.3%**                                                  |
| Latency Tier         | Good                                                       |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| 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 [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **7,391.1 km** |
| Vacuum RTT floor                              | **49.31 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **72.38 ms**   |
| Low-latency fiber material floor              | **72.09 ms**   |
| Engineering floor (5% path allowance)         | **76.01 ms**   |
| Research 1.33× mapped-fiber reference         | **96.26 ms**   |
| Estimated unamplified path loss               | **1552.1 dB**  |
| Transparent optical spans / inline amplifiers | **98 / 97**    |
| Published RTT inflation over fiber floor      | **1.91×**      |

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        | **133.73 ms** |
| Average RTT        | **138.5 ms**  |
| Maximum RTT        | **150.99 ms** |
| Standard deviation | **4.36 ms**   |
| Stdev / average    | **3.1%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/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**

* [Hong Kong to Melbourne latency and RTT](/docs/network/latency/pairs/hkg-mel-rtt) — 138.4 ms

**Fastest routes departing Melbourne (MEL)**

* [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms
* [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms
* [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms
* [Melbourne to Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms
* [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms

**Fastest routes arriving at Hong Kong (HKG)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 ms

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

* [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms
* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mel-hkg.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Hong Kong 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/mel-hkg-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.