# Seattle, USA → Hong Kong RTT

🇺🇸 **Seattle, USA (SEA)** → 🇭🇰 **Hong Kong (HKG)**

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

During the 2026-08-16T04:07:28Z round, 50 ICMP echo samples from Seattle to Hong Kong produced an average round-trip time of 130.4 ms, with a minimum of 125.05 ms and a maximum of 145.66 ms. Packet loss was 0%, while jitter of 4.02 ms and a standard deviation of 4.85 ms keep the route in the Good latency tier.

The 10,435.9 km separation gives a vacuum floor of 69.62 ms and a fiber floor of 102.2 ms. The measured average is only 1.28 times the fiber floor, a fiber efficiency of 78.4%, which is a strong result for a trans-Pacific crossing.

Across the 19 outbound routes measured from Seattle in this round, this path ranks 10th. Its standard deviation is about 3.7% of the average, slightly above the 3.28% median deviation-to-average of the route family, so the efficient average comes with a bit more run-to-run variation than the typical route.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **130.4 ms**                                                 |
| Jitter               | **4.02 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **102.2 ms**                                                 |
| Fiber Efficiency     | **78.4%**                                                    |
| 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 [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) 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                      | **10,435.9 km** |
| Vacuum RTT floor                              | **69.62 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **102.2 ms**    |
| Low-latency fiber material floor              | **101.79 ms**   |
| Engineering floor (5% path allowance)         | **107.32 ms**   |
| Research 1.33× mapped-fiber reference         | **135.92 ms**   |
| Estimated unamplified path loss               | **2191.5 dB**   |
| Transparent optical spans / inline amplifiers | **137 / 136**   |
| 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        | **125.05 ms** |
| Average RTT        | **130.4 ms**  |
| Maximum RTT        | **145.66 ms** |
| Standard deviation | **4.85 ms**   |
| Stdev / average    | **3.7%**      |

## Route Context

* Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* 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 Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms

**Fastest routes departing Seattle (SEA)**

* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 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
* [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms

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

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