# Taipei, Taiwan β†’ Johannesburg, South Africa RTT πŸ‡ΉπŸ‡Ό **Taipei, Taiwan (TPE)** β†’ πŸ‡ΏπŸ‡¦ **Johannesburg, South Africa (JNB)** Measurement round: `2026-08-16T04:07:28Z`. Taipei to Johannesburg averaged 331 ms, compared with a 112.87 ms city-centre fiber reference. The difference cannot be assigned to a particular cable or carrier from RTT alone. Standard deviation was 6.31 ms, or 1.9% of the average. This describes variation within the sample without identifying its cause. ## Latency Summary | Metric | Value | | -------------------- | ---------------------------------------------------------- | | RTT | **331 ms** | | Jitter | **5.35 ms** | | Packet Loss | **0%** | | Standard Fiber Floor | **112.87 ms** | | Fiber Efficiency | **34.1%** | | Latency Tier | High | | Source Region | [Asia Pacific](/docs/network/latency/regions/asia-pacific) | | Destination Region | [Africa](/docs/network/latency/regions/africa) | ## 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: [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). These are not facility coordinates or a surveyed cable path. | Physical Reference | Value | | --------------------------------------------- | --------------- | | WGS-84 geodesic distance | **11,525.4 km** | | Vacuum RTT floor | **76.89 ms** | | Standard fiber RTT floor ($n_g=1.4679$) | **112.87 ms** | | Low-latency fiber material floor | **112.41 ms** | | Engineering floor (5% path allowance) | **118.52 ms** | | Research 1.33Γ— mapped-fiber reference | **150.11 ms** | | Estimated unamplified path loss | **2420.3 dB** | | Transparent optical spans / inline amplifiers | **152 / 151** | | Published RTT inflation over fiber floor | **2.93Γ—** | 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 | **322.36 ms** | | Average RTT | **331 ms** | | Maximum RTT | **356.12 ms** | | Standard deviation | **6.31 ms** | | Stdev / average | **1.9%** | ## Route Context * Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei) * Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg) * Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) β†’ [Africa](/docs/network/latency/regions/africa) * 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** * [Johannesburg to Taipei latency and RTT](/docs/network/latency/pairs/jnb-tpe-rtt): 329.8 ms **Fastest routes departing Taipei (TPE)** * [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt): 15.5 ms * [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt): 31.9 ms * [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt): 44.3 ms * [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt): 115.8 ms * [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt): 132 ms **Fastest routes arriving at Johannesburg (JNB)** * [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt): 171.9 ms * [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt): 172.1 ms * [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt): 179.6 ms * [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt): 180.9 ms * [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt): 188.4 ms **Same corridor (Asia Pacific β†’ Africa)** * [Singapore to Johannesburg latency and RTT](/docs/network/latency/pairs/sin-jnb-rtt): 312.6 ms * [Hong Kong to Johannesburg latency and RTT](/docs/network/latency/pairs/hkg-jnb-rtt): 316.7 ms * [Tokyo to Johannesburg latency and RTT](/docs/network/latency/pairs/tyo-jnb-rtt): 359.2 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/tpe-jnb.pings.{csv,json,yaml}`. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Taipei β†’ Johannesburg 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/tpe-jnb-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.