# 🇭🇰 Hong Kong Ping & Network Latency (HKG) | AS203314

## 🇭🇰 Hong Kong (HKG)

Hong Kong is Asia's premier financial and interconnection hub, offering direct access to one of the world's densest fiber markets. Hats Network's HKG PoP is a cornerstone of the Asia-Pacific backbone.

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

This page provides round-trip time (RTT) latency metrics between the **Hong Kong (HKG)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Hong Kong, Hong Kong (Asia Pacific)
* **Region:** Asia Pacific
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 1819729](https://www.geonames.org/1819729) — 22.27832, 114.17469
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** HKG3
* **Upstream transit:** HE / Cogent / CDN77
* **Peering / IX:** Equinix IX / HKIX

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                         |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇭🇰 Hong Kong (HKG) → 🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt) (**14.7 ms**) — Ultra-Low |
| Slowest Route         | [🇭🇰 Hong Kong (HKG) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/hkg-jnb-rtt) (**316.7 ms**)      |
| Average RTT           | **151.1 ms**                                                                                                  |
| Average Jitter        | **1.15 ms**                                                                                                   |
| Average Packet Loss   | **0.06%**                                                                                                     |
| Best Fiber Efficiency | **80.1%**                                                                                                     |
| Intra-Region Peers    | 5 PoPs in Asia Pacific                                                                                        |
| Total Routes          | 19 outbound / 19 inbound (100% coverage)                                                                      |

> Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the [theoretical fiber latency methodology](/docs/network/latency/theoretical-fiber-latency).

## Geographic & Network Position

Hong Kong sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **14.7 ms** (Taipei (TPE)) to **138.4 ms** (Melbourne (MEL)).

Hong Kong is a dense Asia-Pacific interconnection hub; regional submarine systems such as APG link it with Taiwan, Japan and Southeast Asia.

## Outbound Latency from Hong Kong (HKG)

Round-trip time in milliseconds **from Hong Kong** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇹🇼 Taipei (TPE)       | **[14.7](/docs/network/latency/pairs/hkg-tpe-rtt)**  | 7.94 ms     | 54%        | 0.14 ms | 0.08% | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[31.5](/docs/network/latency/pairs/hkg-sin-rtt)**  | 25.24 ms    | 80.1%      | 0.33 ms | 0.05% | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[44.9](/docs/network/latency/pairs/hkg-tyo-rtt)**  | 28.24 ms    | 62.9%      | 0.23 ms | 0.08% | Excellent |
| 🇷🇺 Moscow (MOW)       | **[118.2](/docs/network/latency/pairs/hkg-mow-rtt)** | 70.05 ms    | 59.3%      | 1.17 ms | 0.11% | Good      |
| 🇺🇸 Seattle (SEA)      | **[131.6](/docs/network/latency/pairs/hkg-sea-rtt)** | 102.2 ms    | 77.7%      | 0.82 ms | 0.05% | Good      |
| 🇦🇺 Sydney (SYD)       | **[137.2](/docs/network/latency/pairs/hkg-syd-rtt)** | 71.97 ms    | 52.5%      | 0.86 ms | 0.17% | Good      |
| 🇦🇺 Melbourne (MEL)    | **[138.4](/docs/network/latency/pairs/hkg-mel-rtt)** | 72.38 ms    | 52.3%      | 1.41 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[145](/docs/network/latency/pairs/hkg-lax-rtt)**   | 114.3 ms    | 78.8%      | 1.4 ms  | 0.06% | Good      |
| 🇩🇪 Berlin (BER)       | **[145.1](/docs/network/latency/pairs/hkg-ber-rtt)** | 85.85 ms    | 59.2%      | 0.83 ms | 0.18% | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[150.7](/docs/network/latency/pairs/hkg-fra-rtt)** | 89.87 ms    | 59.6%      | 1.66 ms | 0%    | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[154.4](/docs/network/latency/pairs/hkg-ams-rtt)** | 91.05 ms    | 59%        | 0.87 ms | 0%    | Fair      |
| 🇬🇧 London (LON)       | **[158.7](/docs/network/latency/pairs/hkg-lon-rtt)** | 94.44 ms    | 59.5%      | 0.8 ms  | 0%    | Fair      |
| 🇫🇷 Paris (PAR)        | **[159.4](/docs/network/latency/pairs/hkg-par-rtt)** | 94.48 ms    | 59.3%      | 1.21 ms | 0.07% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[165.4](/docs/network/latency/pairs/hkg-mrs-rtt)** | 95.48 ms    | 57.7%      | 0.85 ms | 0.09% | Fair      |
| 🇺🇸 New York (NYC)     | **[184.7](/docs/network/latency/pairs/hkg-nyc-rtt)** | 127.11 ms   | 68.8%      | 0.98 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[186.2](/docs/network/latency/pairs/hkg-iad-rtt)** | 128.37 ms   | 68.9%      | 1.54 ms | 0.04% | Fair      |
| 🇺🇸 Miami (MIA)        | **[201.1](/docs/network/latency/pairs/hkg-mia-rtt)** | 141.69 ms   | 70.5%      | 0.93 ms | 0.05% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[287.6](/docs/network/latency/pairs/hkg-gru-rtt)** | 176.86 ms   | 61.5%      | 2.69 ms | 0.03% | High      |
| 🇿🇦 Johannesburg (JNB) | **[316.7](/docs/network/latency/pairs/hkg-jnb-rtt)** | 104.93 ms   | 33.1%      | 3.12 ms | 0%    | High      |

## Fastest Routes to Hong Kong (HKG)

The 10 fastest measured routes **to Hong Kong**, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.

| Rank | Source                 | Avg RTT                                                 | Min       | Max       | Stdev   |
| ---- | ---------------------- | ------------------------------------------------------- | --------- | --------- | ------- |
| 1    | 🇹🇼 Taipei (TPE)      | **[15.5 ms](/docs/network/latency/pairs/tpe-hkg-rtt)**  | 15.09 ms  | 17.58 ms  | 0.41 ms |
| 2    | 🇸🇬 Singapore (SIN)   | **[30.8 ms](/docs/network/latency/pairs/sin-hkg-rtt)**  | 30.29 ms  | 33.37 ms  | 0.58 ms |
| 3    | 🇯🇵 Tokyo (TYO)       | **[44.8 ms](/docs/network/latency/pairs/tyo-hkg-rtt)**  | 43.35 ms  | 48.43 ms  | 1.13 ms |
| 4    | 🇷🇺 Moscow (MOW)      | **[118.6 ms](/docs/network/latency/pairs/mow-hkg-rtt)** | 116.41 ms | 127.8 ms  | 2.24 ms |
| 5    | 🇺🇸 Seattle (SEA)     | **[130.4 ms](/docs/network/latency/pairs/sea-hkg-rtt)** | 125.05 ms | 145.66 ms | 4.85 ms |
| 6    | 🇦🇺 Sydney (SYD)      | **[135.7 ms](/docs/network/latency/pairs/syd-hkg-rtt)** | 124.18 ms | 155.08 ms | 6.42 ms |
| 7    | 🇦🇺 Melbourne (MEL)   | **[138.5 ms](/docs/network/latency/pairs/mel-hkg-rtt)** | 133.73 ms | 150.99 ms | 4.36 ms |
| 8    | 🇩🇪 Berlin (BER)      | **[144.9 ms](/docs/network/latency/pairs/ber-hkg-rtt)** | 140.42 ms | 158.73 ms | 3.7 ms  |
| 9    | 🇺🇸 Los Angeles (LAX) | **[146.5 ms](/docs/network/latency/pairs/lax-hkg-rtt)** | 143.01 ms | 158.89 ms | 3.29 ms |
| 10   | 🇩🇪 Frankfurt (FRA)   | **[152 ms](/docs/network/latency/pairs/fra-hkg-rtt)**   | 144.15 ms | 171.03 ms | 6.84 ms |

## Inbound Latency to Hong Kong (HKG)

Round-trip time in milliseconds **from all other PoPs to Hong Kong**. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.

| Source                  | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇹🇼 Taipei (TPE)       | **[15.5](/docs/network/latency/pairs/tpe-hkg-rtt)**  | 7.94 ms     | 51.2%      | 0.16 ms | 0.02% | Ultra-Low |
| 🇸🇬 Singapore (SIN)    | **[30.8](/docs/network/latency/pairs/sin-hkg-rtt)**  | 25.24 ms    | 81.9%      | 0.23 ms | 0.1%  | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[44.8](/docs/network/latency/pairs/tyo-hkg-rtt)**  | 28.24 ms    | 63%        | 0.45 ms | 0.07% | Excellent |
| 🇷🇺 Moscow (MOW)       | **[118.6](/docs/network/latency/pairs/mow-hkg-rtt)** | 70.05 ms    | 59.1%      | 0.77 ms | 0.13% | Good      |
| 🇺🇸 Seattle (SEA)      | **[130.4](/docs/network/latency/pairs/sea-hkg-rtt)** | 102.2 ms    | 78.4%      | 0.7 ms  | 0%    | Good      |
| 🇦🇺 Sydney (SYD)       | **[135.7](/docs/network/latency/pairs/syd-hkg-rtt)** | 71.97 ms    | 53%        | 0.65 ms | 0.19% | Good      |
| 🇦🇺 Melbourne (MEL)    | **[138.5](/docs/network/latency/pairs/mel-hkg-rtt)** | 72.38 ms    | 52.3%      | 1.39 ms | 0.19% | Good      |
| 🇩🇪 Berlin (BER)       | **[144.9](/docs/network/latency/pairs/ber-hkg-rtt)** | 85.85 ms    | 59.3%      | 1.29 ms | 0.08% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[146.5](/docs/network/latency/pairs/lax-hkg-rtt)** | 114.3 ms    | 78%        | 1.42 ms | 0%    | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[152](/docs/network/latency/pairs/fra-hkg-rtt)**   | 89.87 ms    | 59.1%      | 1.18 ms | 0%    | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[155.9](/docs/network/latency/pairs/ams-hkg-rtt)** | 91.05 ms    | 58.4%      | 1.21 ms | 0.05% | Fair      |
| 🇫🇷 Paris (PAR)        | **[160.1](/docs/network/latency/pairs/par-hkg-rtt)** | 94.48 ms    | 59%        | 1.29 ms | 0.05% | Fair      |
| 🇬🇧 London (LON)       | **[160.6](/docs/network/latency/pairs/lon-hkg-rtt)** | 94.44 ms    | 58.8%      | 0.84 ms | 0.07% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[166.4](/docs/network/latency/pairs/mrs-hkg-rtt)** | 95.48 ms    | 57.4%      | 1.49 ms | 0%    | Fair      |
| 🇺🇸 New York (NYC)     | **[187.1](/docs/network/latency/pairs/nyc-hkg-rtt)** | 127.11 ms   | 67.9%      | 1.76 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[187.2](/docs/network/latency/pairs/iad-hkg-rtt)** | 128.37 ms   | 68.6%      | 1 ms    | 0.05% | Fair      |
| 🇺🇸 Miami (MIA)        | **[199.5](/docs/network/latency/pairs/mia-hkg-rtt)** | 141.69 ms   | 71%        | 2.35 ms | 0.06% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[273.5](/docs/network/latency/pairs/gru-hkg-rtt)** | 176.86 ms   | 64.7%      | 2.57 ms | 0%    | High      |
| 🇿🇦 Johannesburg (JNB) | **[318](/docs/network/latency/pairs/jnb-hkg-rtt)**   | 104.93 ms   | 33%        | 3.32 ms | 0.19% | High      |

## Asia Pacific Peers

Hong Kong is one of 6 Hats Network PoPs in **Asia Pacific**. Intra-region routes offer the lowest latency and highest path diversity.

| PoP                                     | Code | Country   | RTT (ms)  | Tier      |
| --------------------------------------- | ---- | --------- | --------- | --------- |
| [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL  | Australia | **138.4** | Good      |
| [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN  | Singapore | **31.5**  | Excellent |
| [🇦🇺 Sydney (SYD)](./syd-sydney)       | SYD  | Australia | **137.2** | Good      |
| [🇹🇼 Taipei (TPE)](./tpe-taipei)       | TPE  | Taiwan    | **14.7**  | Ultra-Low |
| [🇯🇵 Tokyo (TYO)](./tyo-tokyo)         | TYO  | Japan     | **44.9**  | Excellent |

## Frequently Asked Questions

**What is the fastest route to Hong Kong?**

The fastest measured route to Hong Kong (HKG) is [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt), averaging **15.5 ms** RTT (Ultra-Low).

**What is the fastest route from Hong Kong?**

The fastest measured route from Hong Kong (HKG) is [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt), averaging **14.7 ms** RTT (Ultra-Low).

**How well connected is Hong Kong to the Hats Network backbone?**

Hong Kong (HKG) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Hong Kong (HKG) → Johannesburg (JNB)](/docs/network/latency/pairs/hkg-jnb-rtt), averages **316.7 ms** RTT.

## Open Data

Measured latency data for Hong Kong (HKG) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) as part of the Hats Network open latency dataset:

* **Per-route files** — every directed route from Hong Kong is published as `hkg-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [hkg-tpe.pings.csv](/opendata/latency/latest/pairs/hkg-tpe.pings.csv), the 50-probe ICMP echo round for [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/hkg-hong-kong).
- **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.