Measured ICMP round-trip time between Taipei, Taiwan and Johannesburg, South Africa: 331 ms average latency, 0% packet loss, 5.35 ms jitter across 50 samples.

🇹🇼 Taipei, Taiwan (TPE) → 🇿🇦 Johannesburg, South Africa (JNB)

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

The Taipei–Johannesburg ICMP echo run from round 2026-08-16T04:07:28Z produced a 331 ms average RTT, with a minimum of 322.36 ms, a maximum of 356.12 ms, and 5.35 ms jitter across 50 samples. Packet loss was zero, and the measured latency tier was High.

For this 19-route outbound round, Taipei–Johannesburg ranked 19th by average latency. Its standard deviation was 6.31 ms, just 1.91% of the mean, well below the 3.28% median variability across the measured outbound set—so the long path was consistent despite its High latency tier.

With a geodesic distance of 11,525.4 km, the observed mean is 2.93 times the 112.87 ms fiber-floor estimate, a 34.1% fiber efficiency. As Johannesburg is this network's African anchor, the profile offers a useful long-haul benchmark for Southern Africa connectivity, while ICMP RTT alone should not be treated as an application performance predictor.

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
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: TPE → JNB

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 331.0 ± 0.89 ms (SE)

Sample distribution: box = interquartile range (327.3–333.8 ms), median 329.7 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 (112.9 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	341.12
2	100	332.90
3	200	342.56
4	300	339.20
5	400	333.20
6	500	328.53
7	600	327.47
8	700	329.25
9	800	335.65
10	900	327.55
11	1000	324.35
12	1100	329.28
13	1200	333.37
14	1300	328.84
15	1400	325.63
16	1500	324.58
17	1600	356.12
18	1700	334.51
19	1800	327.37
20	1900	332.49
21	2000	328.04
22	2100	333.24
23	2200	331.13
24	2300	334.92
25	2400	331.36
26	2500	337.26
27	2600	327.30
28	2700	323.78
29	2800	323.86
30	2900	323.41
31	3000	332.24
32	3100	327.52
33	3200	335.26
34	3300	327.97
35	3400	325.45
36	3500	332.31
37	3600	333.97
38	3700	329.07
39	3800	335.48
40	3900	340.37
41	4000	341.48
42	4100	332.31
43	4200	331.95
44	4300	328.35
45	4400	324.13
46	4500	323.04
47	4600	324.99
48	4700	323.45
49	4800	322.36
50	4900	330.03

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.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Taipei (25.05306, 121.52639) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.

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×

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	322.36 ms
Average RTT	331 ms
Maximum RTT	356.12 ms
Standard deviation	6.31 ms
Stdev / average	1.9%

RTT trend

Estimated route stability across the selected time window.

Average: 331.2 ms
Minimum: 328.1 ms
Maximum: 334.5 ms
Average loss: 0.01%

Route Context

Departure PoP: Taipei (TPE)
Destination PoP: Johannesburg (JNB)
Region overview: Asia Pacific → Africa
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Johannesburg to Taipei latency and RTT — 329.8 ms

Fastest routes departing Taipei (TPE)

Taipei to Hong Kong latency and RTT — 15.5 ms
Taipei to Tokyo latency and RTT — 31.9 ms
Taipei to Singapore latency and RTT — 44.3 ms
Taipei to Seattle latency and RTT — 115.8 ms
Taipei to Los Angeles latency and RTT — 132 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
Hong Kong to Johannesburg latency and RTT — 316.7 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/tpe-jnb.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → 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.

Taipei, Taiwan → Johannesburg, South Africa RTT