Johannesburg to Tokyo ping and RTT: 362.7 ms, 9.59 ms jitter, 132.57 ms fiber floor, and 36.6% efficiency across AS203314. Updated 2026-08-10.

🇿🇦 This page compares the published ping and round-trip time (RTT) from Johannesburg (JNB) to 🇯🇵 Tokyo (TYO) with vacuum and optical-fiber physical limits.

As of August 10, 2026, the Johannesburg → Tokyo route on Hats Network averages 362.7 ms RTT across a 50-sample daily ICMP echo measurement round, 2.74× the theoretical fiber-floor limit of 132.57 ms.

Among the 19 measured routes departing Johannesburg, this route ranks 17th fastest by average RTT.

With a stdev-to-average ratio of 2.6%, this route is more stable than the network median of 3.1%. Across the round, per-probe RTT ranged from 350.48 ms to 393 ms with a standard deviation of 9.43 ms.

Latency Summary

Metric	Value
RTT	362.7 ms
Jitter	9.59 ms
Packet Loss	0%
Standard Fiber Floor	132.57 ms
Fiber Efficiency	36.6%
Latency Tier	High
Source Region	Africa
Destination Region	Asia Pacific

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

50 ICMP echo samples at 100 ms intervals · round 2026-08-10 · avg 362.7 ± 1.33 ms (SE)

Sample distribution: box = interquartile range (356.6–364.9 ms), median 359.9 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 (132.6 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	359.90
2	100	379.43
3	200	384.28
4	300	360.18
5	400	359.49
6	500	354.03
7	600	366.43
8	700	359.82
9	800	369.97
10	900	360.83
11	1000	357.97
12	1100	354.82
13	1200	363.90
14	1300	359.92
15	1400	360.03
16	1500	370.62
17	1600	356.57
18	1700	352.97
19	1800	371.22
20	1900	359.68
21	2000	358.43
22	2100	356.87
23	2200	359.84
24	2300	351.56
25	2400	353.39
26	2500	354.11
27	2600	356.45
28	2700	350.48
29	2800	361.28
30	2900	353.40
31	3000	384.53
32	3100	376.42
33	3200	358.17
34	3300	353.94
35	3400	393.00
36	3500	365.03
37	3600	359.89
38	3700	359.42
39	3800	360.83
40	3900	359.59
41	4000	377.29
42	4100	362.46
43	4200	352.46
44	4300	354.24
45	4400	378.71
46	4500	364.04
47	4600	357.06
48	4700	373.87
49	4800	364.44
50	4900	361.74

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 Johannesburg (-26.20227, 28.04363) and Tokyo (35.68950, 139.69171). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	13,537.7 km
Vacuum RTT floor	90.31 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	132.57 ms
Low-latency fiber material floor	132.04 ms
Engineering floor (5% path allowance)	139.22 ms
Research 1.33× mapped-fiber reference	176.32 ms
Estimated unamplified path loss	2842.9 dB
Transparent optical spans / inline amplifiers	178 / 177
Published RTT inflation over fiber floor	2.74×

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-10) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	350.48 ms
Average RTT	362.7 ms
Maximum RTT	393 ms
Standard deviation	9.43 ms
Stdev / average	2.6%

RTT trend

Estimated route stability across the selected time window.

Average: 363.4 ms
Minimum: 360.7 ms
Maximum: 366.9 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Tokyo to Johannesburg latency and RTT — 360.5 ms

Fastest routes departing Johannesburg (JNB)

Johannesburg to London latency and RTT — 158 ms
Johannesburg to Amsterdam latency and RTT — 163.2 ms
Johannesburg to Paris latency and RTT — 164.4 ms
Johannesburg to Frankfurt latency and RTT — 166 ms
Johannesburg to Marseille latency and RTT — 172 ms

Fastest routes arriving at Tokyo (TYO)

Taipei to Tokyo latency and RTT — 31.9 ms
Hong Kong to Tokyo latency and RTT — 45.7 ms
Singapore to Tokyo latency and RTT — 69.8 ms
Seattle to Tokyo latency and RTT — 84 ms
Los Angeles to Tokyo latency and RTT — 100.7 ms

Same corridor (Africa → Asia Pacific)

Johannesburg to Singapore latency and RTT — 309.5 ms
Johannesburg to Hong Kong latency and RTT — 318.4 ms
Johannesburg to Taipei latency and RTT — 333 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/jnb-tyo.pings.{csv,json,yaml}. When citing, include the route, the measurement round date, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Tokyo round 2026-08-10, CC BY 4.0".

Data auto-generated on August 10, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Johannesburg to Tokyo Latency, Ping & RTT | AS203314