Hong Kong → Johannesburg, South Africa RTT
Measured ICMP echo RTT from Hong Kong (Hong Kong) to Johannesburg, South Africa: 316.7 ms average, 0% loss, high latency tier in round 2026-08-16T04:07:28Z.
🇭🇰 Hong Kong (HKG) → 🇿🇦 Johannesburg, South Africa (JNB)
Measurement round: 2026-08-16T04:07:28Z.
Round 2026-08-16T04:07:28Z measured ICMP echo RTT between Hong Kong and Johannesburg at an average of 316.7 ms, with a 301.28 ms minimum, a 350.25 ms maximum, and zero packet loss across 50 samples. The 11.99 ms standard deviation and 10.88 ms jitter are noticeable but not extreme for an intercontinental route, and the high latency tier reflects the distance.
This path ranks 19th out of the 19 outbound routes in this round, placing it at the high-latency end of the measured set. Its variability ratio of about 3.8% is close to the 3.28% network-wide median, so the long delay is consistent rather than erratic.
The great-circle distance is 10,715.5 km, giving a vacuum floor of 71.49 ms and a fiber floor of 104.93 ms. The observed RTT is 3.02 times the fiber floor, a fiber efficiency of 33.1%, reflecting the practical geography of long-haul intercontinental cabling; even with 0% loss, a high RTT floor should be expected on this path.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 316.7 ms |
| Jitter | 10.88 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 104.93 ms |
| Fiber Efficiency | 33.1% |
| Latency Tier | High |
| Source Region | Asia Pacific |
| Destination Region | Africa |
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.
Ping series: HKG → JNB
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 316.7 ± 1.70 ms (SE)
Sample distribution: box = interquartile range (307.7–321.4 ms), median 315.5 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (104.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 321.69 |
| 2 | 100 | 346.29 |
| 3 | 200 | 331.90 |
| 4 | 300 | 326.75 |
| 5 | 400 | 310.19 |
| 6 | 500 | 326.48 |
| 7 | 600 | 345.08 |
| 8 | 700 | 314.61 |
| 9 | 800 | 317.47 |
| 10 | 900 | 307.68 |
| 11 | 1000 | 303.63 |
| 12 | 1100 | 319.63 |
| 13 | 1200 | 347.63 |
| 14 | 1300 | 320.81 |
| 15 | 1400 | 321.05 |
| 16 | 1500 | 310.72 |
| 17 | 1600 | 304.80 |
| 18 | 1700 | 314.16 |
| 19 | 1800 | 312.30 |
| 20 | 1900 | 307.68 |
| 21 | 2000 | 306.72 |
| 22 | 2100 | 321.58 |
| 23 | 2200 | 317.93 |
| 24 | 2300 | 315.81 |
| 25 | 2400 | 350.25 |
| 26 | 2500 | 317.59 |
| 27 | 2600 | 317.33 |
| 28 | 2700 | 308.79 |
| 29 | 2800 | 315.11 |
| 30 | 2900 | 319.27 |
| 31 | 3000 | 321.39 |
| 32 | 3100 | 306.67 |
| 33 | 3200 | 303.90 |
| 34 | 3300 | 319.84 |
| 35 | 3400 | 330.79 |
| 36 | 3500 | 321.41 |
| 37 | 3600 | 307.80 |
| 38 | 3700 | 308.64 |
| 39 | 3800 | 326.12 |
| 40 | 3900 | 308.04 |
| 41 | 4000 | 302.17 |
| 42 | 4100 | 301.28 |
| 43 | 4200 | 317.68 |
| 44 | 4300 | 311.38 |
| 45 | 4400 | 303.72 |
| 46 | 4500 | 301.62 |
| 47 | 4600 | 303.65 |
| 48 | 4700 | 301.52 |
| 49 | 4800 | 322.65 |
| 50 | 4900 | 313.80 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Hong Kong (22.27832, 114.17469) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 10,715.5 km |
| Vacuum RTT floor | 71.49 ms |
| Standard fiber RTT floor () | 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.02× |
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.
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 | 301.28 ms |
| Average RTT | 316.7 ms |
| Maximum RTT | 350.25 ms |
| Standard deviation | 11.99 ms |
| Stdev / average | 3.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 317.0 ms
- Minimum
- 313.0 ms
- Maximum
- 319.8 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Hong Kong (HKG)
- Destination PoP: Johannesburg (JNB)
- Region overview: Asia Pacific → Africa
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
Fastest routes departing Hong Kong (HKG)
- Hong Kong to Taipei latency and RTT — 14.7 ms
- Hong Kong to Singapore latency and RTT — 31.5 ms
- Hong Kong to Tokyo latency and RTT — 44.9 ms
- Hong Kong to Moscow latency and RTT — 118.2 ms
- Hong Kong to Seattle latency and RTT — 131.6 ms
Fastest routes arriving at Johannesburg (JNB)
- Amsterdam to Johannesburg latency and RTT — 171.9 ms
- Berlin to Johannesburg latency and RTT — 172.1 ms
- London to Johannesburg latency and RTT — 179.6 ms
- Paris to Johannesburg latency and RTT — 180.9 ms
- Frankfurt to Johannesburg latency and RTT — 188.4 ms
Same corridor (Asia Pacific → Africa)
- Singapore to Johannesburg latency and RTT — 312.6 ms
- Taipei to Johannesburg latency and RTT — 331 ms
- Tokyo to Johannesburg latency and RTT — 359.2 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. Per-pair files are available at /opendata/latency/latest/pairs/hkg-jnb.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 → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0".
Data auto-generated on August 16, 2026. Explore the full interactive latency matrix or browse more city-pair routes.