# Melbourne, Australia → Taipei, Taiwan RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇹🇼 **Taipei, Taiwan (TPE)**

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

In the 2026-08-16T04:07:28Z measurement round, Melbourne to Taipei ICMP RTT averaged 143.2 ms, with a minimum of 135 ms and a maximum of 166.26 ms across 50 samples; packet loss was 0 percent. The 6.42 ms jitter and 7.11 ms standard deviation show a path that remains usable and stable despite a roughly 31 ms spread between best and worst samples.

Within the 19 outbound routes in this measurement set, this pairing ranks fifth by average RTT. Its relative variation of about 5.0 percent is above the 3.28 percent median for the same set, so the route is quicker than most of the set while being a little less uniform than the typical route.

The geodesic distance of 7,377.8 km sets a straight-line fiber floor of 72.25 ms. The measured average is 1.98 times that floor, for 50.5 percent fiber efficiency, and with zero packet loss the extra delay is best attributed to the longer path the packets actually travel rather than to loss or retransmission.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **143.2 ms**                                               |
| Jitter               | **6.42 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **72.25 ms**                                               |
| Fiber Efficiency     | **50.5%**                                                  |
| 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 [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **7,377.8 km** |
| Vacuum RTT floor                              | **49.22 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **72.25 ms**   |
| Low-latency fiber material floor              | **71.96 ms**   |
| Engineering floor (5% path allowance)         | **75.87 ms**   |
| Research 1.33× mapped-fiber reference         | **96.09 ms**   |
| Estimated unamplified path loss               | **1549.3 dB**  |
| Transparent optical spans / inline amplifiers | **97 / 96**    |
| Published RTT inflation over fiber floor      | **1.98×**      |

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        | **135 ms**    |
| Average RTT        | **143.2 ms**  |
| Maximum RTT        | **166.26 ms** |
| Standard deviation | **7.11 ms**   |
| Stdev / average    | **5.0%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* 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**

* [Taipei to Melbourne latency and RTT](/docs/network/latency/pairs/tpe-mel-rtt) — 142 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 Hong Kong latency and RTT](/docs/network/latency/pairs/mel-hkg-rtt) — 138.5 ms
* [Melbourne to Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms

**Fastest routes arriving at Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms

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

* [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms
* [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

## 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-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Taipei 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-tpe-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.