# Tokyo, Japan → Melbourne, Australia RTT

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

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

In the 2026-08-16T04:07:28Z measurement round, the Tokyo-to-Melbourne path averaged 113.9 ms across 50 ICMP probes, with a minimum of 107.58 ms and a maximum of 128.46 ms. The 4.6 ms standard deviation and 4.76 ms jitter indicate a modest spread around that average, while 0% packet loss meant every probe reached its destination.

The great-circle distance of 8,156.1 km yields a vacuum RTT floor of 54.41 ms and a theoretical fiber RTT floor of 79.87 ms. The observed average is 1.43 times the fiber floor, placing fiber efficiency at 70.1 percent; the minimum sample of 107.58 ms stays about 27.7 ms above that floor.

In this round's 19-route outbound set, this pair ranked 7th, putting its absolute latency in the upper-middle range. However, its standard deviation is about 4.0 percent of the average, above the 3.28 percent median relative variability for the set, so the Good latency tier comes with more sample-to-sample variation than typical for the round.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **113.9 ms**                                               |
| Jitter               | **4.76 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **79.87 ms**                                               |
| Fiber Efficiency     | **70.1%**                                                  |
| 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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) 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                      | **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.43×**      |

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        | **107.58 ms** |
| Average RTT        | **113.9 ms**  |
| Maximum RTT        | **128.46 ms** |
| Standard deviation | **4.6 ms**    |
| Stdev / average    | **4.0%**      |

## Route Context

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

* [Melbourne to Tokyo latency and RTT](/docs/network/latency/pairs/mel-tyo-rtt) — 112 ms

**Fastest routes departing Tokyo (TYO)**

* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms
* [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.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
* [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
* [Los Angeles to Melbourne latency and RTT](/docs/network/latency/pairs/lax-mel-rtt) — 148.2 ms

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

* [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-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/tyo-mel.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → 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/tyo-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.