# Hong Kong → Miami, USA RTT

🇭🇰 **Hong Kong (HKG)** → 🇺🇸 **Miami, USA (MIA)**

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

For measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Hong Kong to Miami returned an average RTT of 201.1 ms, with a minimum of 194.49 ms and a maximum of 226.67 ms. Packet loss was 0%, and jitter was 4.97 ms.

The geodesic distance is 14,468.4 km, and the measured average is 1.42 times the fiber floor, which corresponds to 70.5% fiber-path efficiency. The 6.05 ms standard deviation equals about 3.0% of the average, slightly below the 3.28% median relative variability across the 19 outbound routes in this round.

This route ranks 17th among those 19 outbound paths, so it sits near the slower end of the Hong Kong outbound set. Its Fair latency tier and 201 ms average reflect a long-haul route where absolute delay is substantial, yet the zero-loss result and contained jitter keep the path predictable.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **201.1 ms**                                                 |
| Jitter               | **4.97 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **141.69 ms**                                                |
| Fiber Efficiency     | **70.5%**                                                    |
| 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 [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) 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                      | **14,468.4 km** |
| Vacuum RTT floor                              | **96.52 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **141.69 ms**   |
| Low-latency fiber material floor              | **141.12 ms**   |
| Engineering floor (5% path allowance)         | **148.79 ms**   |
| Research 1.33× mapped-fiber reference         | **188.44 ms**   |
| Estimated unamplified path loss               | **3038.4 dB**   |
| Transparent optical spans / inline amplifiers | **190 / 189**   |
| Published RTT inflation over fiber floor      | **1.42×**       |

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        | **194.49 ms** |
| Average RTT        | **201.1 ms**  |
| Maximum RTT        | **226.67 ms** |
| Standard deviation | **6.05 ms**   |
| Stdev / average    | **3.0%**      |

## Route Context

* Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* 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 Hong Kong latency and RTT](/docs/network/latency/pairs/mia-hkg-rtt) — 199.5 ms

**Fastest routes departing Hong Kong (HKG)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms
* [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 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/hkg-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → 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/hkg-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.