# Johannesburg, South Africa β†’ Hong Kong RTT πŸ‡ΏπŸ‡¦ **Johannesburg, South Africa (JNB)** β†’ πŸ‡­πŸ‡° **Hong Kong (HKG)** Measurement round: `2026-08-16T04:07:28Z`. Johannesburg to Hong Kong averaged 318 ms, compared with a 104.93 ms city-centre fiber reference. The difference cannot be assigned to a particular cable or carrier from RTT alone. Standard deviation was 12.41 ms, or 3.9% of the average. This describes variation within the sample without identifying its cause. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **318 ms** | | Jitter | **9.12 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **104.93 ms** | | Fiber Efficiency | **33%** | | Latency Tier | High | | Source Region | [Africa](/docs/network/latency/regions/africa) | | Destination Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | ## Ping Measurement Series 50 ICMP echo probes were recorded in this round. Individual replies and their distribution are shown below. ## Download This Route's Data Download the probe round as CSV, JSON or YAML under CC BY 4.0. [Citation details](#about-this-measurement) include the route and round timestamp. ## Theoretical Fiber Latency The propagation model uses public city-centre coordinates from GeoNames: [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). These are not facility coordinates or a surveyed cable path. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **10,715.5 km** | | Vacuum RTT floor | **71.49 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **104.93 ms** | | Low-latency fiber material floor | **104.51 ms** | | Engineering floor (5% path allowance) | **110.2 ms** | | Research 1.33Γ— mapped-fiber reference | **139.56 ms** | | Estimated unamplified path loss | **2250.3 dB** | | Transparent optical spans / inline amplifiers | **141 / 140** | | Published RTT inflation over fiber floor | **3.03Γ—** | The span count assumes 80 km optical spans. Attenuation is a power-loss term, not a propagation delay. See the [model assumptions and equations](/docs/network/latency/theoretical-fiber-latency). ## Stability & Trend Statistics from the same 50 replies. They describe this probe round, not continuous historical monitoring. | Round Statistic | Value | | ------------------ | ------------- | | Minimum RTT | **302.56 ms** | | Average RTT | **318 ms** | | Maximum RTT | **363.62 ms** | | Standard deviation | **12.41 ms** | | Stdev / average | **3.9%** | ## Route Context * Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong) * Region overview: [Africa](/docs/network/latency/regions/africa) β†’ [Asia Pacific](/docs/network/latency/regions/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 Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt): 316.7 ms **Fastest routes departing Johannesburg (JNB)** * [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt): 158 ms * [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt): 163.2 ms * [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt): 164.4 ms * [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt): 166 ms * [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt): 172 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 (Africa β†’ Asia Pacific)** * [Johannesburg to Singapore latency and RTT](/docs/network/latency/pairs/jnb-sin-rtt): 311.6 ms * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt): 329.8 ms * [Johannesburg to Tokyo latency and RTT](/docs/network/latency/pairs/jnb-tyo-rtt): 360.5 ms ## About This Measurement These ICMP measurements cover the two backbone endpoints. Access networks, routing policy and load can change an end user's result. A probe round is not an SLA. The underlying replies are available under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-hkg.pings.{csv,json,yaml}`. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Johannesburg β†’ Hong Kong round 2026-08-16T04:07:28Z, CC BY 4.0". *** *Round published August 16, 2026. See 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/jnb-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.