ICMP round-trip time measurements from Johannesburg, South Africa to Tokyo, Japan: 360.5 ms average, zero loss, jitter and route efficiency context.

🇿🇦 Johannesburg, South Africa (JNB) → 🇯🇵 Tokyo, Japan (TYO)

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

The 2026-08-16T04:07:28Z ICMP echo RTT measurement from Johannesburg, South Africa to Tokyo, Japan averaged 360.5 ms across 50 samples, with the minimum at 339.64 ms and the maximum at 427.1 ms. The standard deviation was 16.2 ms, jitter was 13.91 ms, and packet loss was 0%, so the path stayed reachable throughout the sample window.

The two cities are 13,537.7 km apart along a great circle, corresponding to a 90.31 ms vacuum floor and a 132.57 ms fiber floor. At 360.5 ms, the measured average is 2.72 times the fiber floor, yielding a fiber efficiency of 36.8% - a long-haul route where absolute latency is heavily influenced by distance.

Within the current outbound route set of 19, this path is ranked 17th. Its standard deviation is about 4.49% of the average, above the group's 3.28% median variability, and the 87.46 ms range between the minimum and maximum shows a wider spread than the average alone suggests.

Latency Summary

Metric	Value
RTT	360.5 ms
Jitter	13.91 ms
Packet Loss	0%
Standard Fiber Floor	132.57 ms
Fiber Efficiency	36.8%
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-16T04:07:28Z · avg 360.5 ± 2.29 ms (SE)

Sample distribution: box = interquartile range (348.9–371.6 ms), median 355.2 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	374.04
2	100	363.80
3	200	365.84
4	300	350.52
5	400	343.84
6	500	348.37
7	600	341.59
8	700	347.68
9	800	372.87
10	900	355.65
11	1000	374.35
12	1100	351.93
13	1200	343.60
14	1300	339.64
15	1400	345.31
16	1500	358.55
17	1600	352.06
18	1700	366.19
19	1800	365.60
20	1900	353.96
21	2000	350.40
22	2100	344.15
23	2200	342.54
24	2300	378.34
25	2400	359.00
26	2500	367.07
27	2600	377.33
28	2700	351.46
29	2800	386.62
30	2900	385.49
31	3000	373.29
32	3100	367.19
33	3200	354.04
34	3300	343.26
35	3400	363.13
36	3500	427.10
37	3600	379.30
38	3700	356.48
39	3800	346.03
40	3900	351.47
41	4000	343.89
42	4100	350.58
43	4200	353.13
44	4300	368.84
45	4400	373.95
46	4500	354.77
47	4600	352.30
48	4700	347.09
49	4800	388.91
50	4900	372.46

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.72×

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	339.64 ms
Average RTT	360.5 ms
Maximum RTT	427.1 ms
Standard deviation	16.2 ms
Stdev / average	4.5%

RTT trend

Estimated route stability across the selected time window.

Average: 359.8 ms
Minimum: 357.4 ms
Maximum: 363.6 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 — 359.2 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 — 44.9 ms
Singapore to Tokyo latency and RTT — 68.9 ms
Seattle to Tokyo latency and RTT — 85 ms
Los Angeles to Tokyo latency and RTT — 101.2 ms

Same corridor (Africa → Asia Pacific)

Johannesburg to Singapore latency and RTT — 311.6 ms
Johannesburg to Hong Kong latency and RTT — 318 ms
Johannesburg to Taipei latency and RTT — 329.8 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 timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Tokyo 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.

Johannesburg, South Africa → Tokyo, Japan RTT