# Melbourne, Australia → Miami, USA RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇺🇸 **Miami, USA (MIA)**

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

For the round from 2026-08-16T04:07:28Z, the 50 ICMP echo probes from Melbourne to Miami recorded an average RTT of 201 ms, with a minimum of 191.59 ms and a maximum of 222.86 ms. Zero packets were lost, while jitter reached 7.48 ms and the standard deviation was 7.91 ms.

This route ranks eighth among the 19 outbound paths measured from Melbourne and lands in the Fair latency tier. The measured spread is about 3.9% of the average, slightly above the network-wide median of 3.28%, so the delay profile is consistent but not exceptionally tight.

Miami's role as the digital gateway between North and South America makes it a distinct destination, but the physical distance of 15,591.9 km still dominates: the vacuum floor is 104.02 ms and the fiber floor is 152.69 ms. The observed average is 1.32 times the fiber floor, with 76% fiber efficiency, indicating the route carries more overhead relative to the theoretical minimum.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **201 ms**                                                   |
| Jitter               | **7.48 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **152.69 ms**                                                |
| Fiber Efficiency     | **76%**                                                      |
| Latency Tier         | Fair                                                         |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific)   |
| Destination Region   | [North America](/docs/network/latency/regions/north-america) |

## 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 [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **15,591.9 km** |
| Vacuum RTT floor                              | **104.02 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **152.69 ms**   |
| Low-latency fiber material floor              | **152.07 ms**   |
| Engineering floor (5% path allowance)         | **160.34 ms**   |
| Research 1.33× mapped-fiber reference         | **203.07 ms**   |
| Estimated unamplified path loss               | **3274.3 dB**   |
| Transparent optical spans / inline amplifiers | **205 / 204**   |
| Published RTT inflation over fiber floor      | **1.32×**       |

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        | **191.59 ms** |
| Average RTT        | **201 ms**    |
| Maximum RTT        | **222.86 ms** |
| Standard deviation | **7.91 ms**   |
| Stdev / average    | **3.9%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america)
* 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**

* [Miami to Melbourne latency and RTT](/docs/network/latency/pairs/mia-mel-rtt) — 200.7 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 Taipei latency and RTT](/docs/network/latency/pairs/mel-tpe-rtt) — 143.2 ms

**Fastest routes arriving at Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms

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

* [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
* [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.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-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Miami 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-mia-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.