# Los Angeles, USA → Hong Kong RTT

🇺🇸 **Los Angeles, USA (LAX)** → 🇭🇰 **Hong Kong (HKG)**

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

For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Los Angeles, USA to Hong Kong averaged 146.5 ms over 50 samples, with a minimum of 143.01 ms and a maximum of 158.89 ms. Zero packet loss and 2.27 ms jitter make the route steady for a trans-Pacific connection.

The route ranked 15th among 19 routes measured from the same origin in this cycle. Its relative variability is around 2.2%, below the 3.28% median across the route set, so the 3.29 ms standard deviation indicates notably consistent latency even at this distance.

Los Angeles is a primary US West Coast landing point for trans-Pacific cables, and Hong Kong is a dense Asia-Pacific interconnection hub. The 11,671.5 km geodesic path has a fiber floor of 114.3 ms; at 146.5 ms the route is 1.28x the floor, a fiber efficiency of 78%, showing the measured path tracks the physical geography well. Despite the lower rank, the high fiber efficiency indicates a physically efficient route.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **146.5 ms**                                                 |
| Jitter               | **2.27 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **114.3 ms**                                                 |
| Fiber Efficiency     | **78%**                                                      |
| 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 [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **11,671.5 km** |
| Vacuum RTT floor                              | **77.86 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **114.3 ms**    |
| Low-latency fiber material floor              | **113.84 ms**   |
| Engineering floor (5% path allowance)         | **120.03 ms**   |
| Research 1.33× mapped-fiber reference         | **152.01 ms**   |
| Estimated unamplified path loss               | **2451 dB**     |
| Transparent optical spans / inline amplifiers | **154 / 153**   |
| Published RTT inflation over fiber floor      | **1.28×**       |

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        | **143.01 ms** |
| Average RTT        | **146.5 ms**  |
| Maximum RTT        | **158.89 ms** |
| Standard deviation | **3.29 ms**   |
| Stdev / average    | **2.2%**      |

## Route Context

* Departure PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles)
* Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* 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**

* [Hong Kong to Los Angeles latency and RTT](/docs/network/latency/pairs/hkg-lax-rtt) — 145 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 Hong Kong (HKG)**

* [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
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 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
* [Los Angeles to Taipei latency and RTT](/docs/network/latency/pairs/lax-tpe-rtt) — 132.9 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-hkg.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 → Hong Kong 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-hkg-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.