# Melbourne, Australia → Tokyo, Japan RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇯🇵 **Tokyo, Japan (TYO)**

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

In the 2026-08-16T04:07:28Z measurement round, Melbourne to Tokyo ICMP RTT averaged 112 ms, with a minimum of 105.34 ms and a maximum of 140.34 ms across 50 samples. Packet loss was 0 percent, and a jitter of 4.68 ms with a standard deviation of 5.58 ms points to a steady long-haul path that rarely drifts outside a narrow band.

This route ranks third by average RTT among the 19 outbound routes in the set. Its variability is roughly 5.0 percent of the mean, which is above the 3.28 percent median for the set, so the route is among the fastest while still showing a bit more spread than the set's typical connection.

For a geodesic distance of 8,156.1 km, the straight-line fiber floor is 79.87 ms. The observed average of 112 ms is only 1.40 times that floor, giving 71.3 percent fiber efficiency and showing that this pairing realizes a large share of the direct-distance speed potential despite its long geography.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **112 ms**                                                 |
| Jitter               | **4.68 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **79.87 ms**                                               |
| Fiber Efficiency     | **71.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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **8,156.1 km** |
| Vacuum RTT floor                              | **54.41 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **79.87 ms**   |
| Low-latency fiber material floor              | **79.55 ms**   |
| Engineering floor (5% path allowance)         | **83.88 ms**   |
| Research 1.33× mapped-fiber reference         | **106.23 ms**  |
| Estimated unamplified path loss               | **1712.8 dB**  |
| Transparent optical spans / inline amplifiers | **108 / 107**  |
| Published RTT inflation over fiber floor      | **1.4×**       |

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        | **105.34 ms** |
| Average RTT        | **112 ms**    |
| Maximum RTT        | **140.34 ms** |
| Standard deviation | **5.58 ms**   |
| Stdev / average    | **5.0%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* 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**

* [Tokyo to Melbourne latency and RTT](/docs/network/latency/pairs/tyo-mel-rtt) — 113.9 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 Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 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 Tokyo (TYO)**

* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms
* [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 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
* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.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-tyo.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Tokyo 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-tyo-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.