# Los Angeles, USA → Melbourne, Australia RTT

🇺🇸 **Los Angeles, USA (LAX)** → 🇦🇺 **Melbourne, Australia (MEL)**

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

For the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Los Angeles to Melbourne measured an average RTT of 148.2 ms, with a minimum of 142.14 ms and a maximum of 162.19 ms.

None of the 50 probes were lost, and the 5.38 ms standard deviation with 4.01 ms jitter indicates a stable path. The average is roughly 19% above the 125 ms fiber-floor estimate for the 12,764 km great-circle distance, so the reported latency is mostly distance-driven.

Within the 19-route outbound set, this Los Angeles-Melbourne path holds 16th position. Its standard deviation is about 3.6% of the average, slightly above the 3.28% median across the set, meaning the path is consistent even though it sits toward the slower end.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **148.2 ms**                                                 |
| Jitter               | **4.01 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **125 ms**                                                   |
| Fiber Efficiency     | **84.3%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| 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 [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368) 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                      | **12,764 km** |
| Vacuum RTT floor                              | **85.15 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **125 ms**    |
| Low-latency fiber material floor              | **124.49 ms** |
| Engineering floor (5% path allowance)         | **131.26 ms** |
| Research 1.33× mapped-fiber reference         | **166.24 ms** |
| Estimated unamplified path loss               | **2680.4 dB** |
| Transparent optical spans / inline amplifiers | **168 / 167** |
| Published RTT inflation over fiber floor      | **1.19×**     |

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        | **142.14 ms** |
| Average RTT        | **148.2 ms**  |
| Maximum RTT        | **162.19 ms** |
| Standard deviation | **5.38 ms**   |
| Stdev / average    | **3.6%**      |

## Route Context

* Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles)
* Destination PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-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 Los Angeles latency and RTT](/docs/network/latency/pairs/mel-lax-rtt) — 148.4 ms

**Fastest routes departing Los Angeles (LAX)**

* [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Los Angeles to Ashburn latency and RTT](/docs/network/latency/pairs/lax-iad-rtt) — 60.4 ms
* [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-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
* [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 (North America → Asia Pacific)**

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