Explore Johannesburg, South Africa to Moscow, Russia ICMP RTT, jitter, packet loss and fiber latency limits on the AS203314 network.

🇿🇦 Johannesburg, South Africa (JNB) → 🇷🇺 Moscow, Russia (MOW)

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

Johannesburg to Moscow averaged 200.7 ms, compared with a 89.37 ms city-centre fiber reference. The difference cannot be assigned to a particular cable or carrier from RTT alone.

Standard deviation was 4.34 ms, or 2.2% of the average. This describes variation within the sample without identifying its cause.

Latency Summary

Metric	Value
RTT	200.7 ms
Jitter	4.03 ms
Packet Loss	0%
Standard Fiber Floor	89.37 ms
Fiber Efficiency	44.5%
Latency Tier	Fair
Source Region	Africa
Destination Region	Europe

Ping Measurement Series

50 ICMP echo probes were recorded in this round. Individual replies and their distribution are shown below.

Ping series: JNB → MOW

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

Sample distribution: box = interquartile range (198.0–202.2 ms), median 199.1 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 (89.4 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	196.62
2	100	202.19
3	200	198.01
4	300	196.37
5	400	197.35
6	500	202.02
7	600	198.73
8	700	198.88
9	800	198.48
10	900	207.37
11	1000	205.72
12	1100	203.71
13	1200	218.52
14	1300	203.40
15	1400	198.67
16	1500	197.46
17	1600	202.28
18	1700	199.86
19	1800	202.23
20	1900	198.79
21	2000	201.72
22	2100	198.31
23	2200	196.67
24	2300	197.95
25	2400	207.51
26	2500	199.62
27	2600	199.93
28	2700	196.97
29	2800	197.34
30	2900	198.45
31	3000	197.32
32	3100	196.07
33	3200	203.30
34	3300	199.18
35	3400	202.22
36	3500	199.81
37	3600	198.71
38	3700	196.94
39	3800	202.62
40	3900	209.07
41	4000	202.11
42	4100	200.96
43	4200	197.56
44	4300	198.52
45	4400	196.48
46	4500	213.21
47	4600	201.62
48	4700	199.06
49	4800	200.77
50	4900	198.34

Download This Route's Data

Download the probe round as CSV, JSON or YAML under CC BY 4.0. Citation details include the route and round timestamp.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The propagation model uses public city-centre coordinates from GeoNames: Johannesburg (-26.20227, 28.04363) and Moscow (55.75204, 37.61781). These are not facility coordinates or a surveyed cable path.

Physical Reference	Value
WGS-84 geodesic distance	9,125.7 km
Vacuum RTT floor	60.88 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	89.37 ms
Low-latency fiber material floor	89.01 ms
Engineering floor (5% path allowance)	93.85 ms
Research 1.33× mapped-fiber reference	118.86 ms
Estimated unamplified path loss	1916.4 dB
Transparent optical spans / inline amplifiers	120 / 119
Published RTT inflation over fiber floor	2.25×

The span count assumes 80 km optical spans. Attenuation is a power-loss term, not a propagation delay. See the model assumptions and equations.

Stability & Trend

Statistics from the same 50 replies. They describe this probe round, not continuous historical monitoring.

Round Statistic	Value
Minimum RTT	196.07 ms
Average RTT	200.7 ms
Maximum RTT	218.52 ms
Standard deviation	4.34 ms
Stdev / average	2.2%

Estimated RTT trend

Modeled comparison, not historical probe measurements.

Average: 200.6 ms
Minimum: 199.1 ms
Maximum: 202.6 ms
Average loss: 0.02%

Route Context

Departure PoP: Johannesburg (JNB)
Destination PoP: Moscow (MOW)
Region overview: Africa → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Moscow to Johannesburg latency and RTT: 201.9 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 Moscow (MOW)

Berlin to Moscow latency and RTT: 28.6 ms
Frankfurt to Moscow latency and RTT: 34.7 ms
Amsterdam to Moscow latency and RTT: 38.1 ms
London to Moscow latency and RTT: 43.5 ms
Paris to Moscow latency and RTT: 44.7 ms

Same corridor (Africa → Europe)

Johannesburg to Berlin latency and RTT: 172.1 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. Per-pair files are available at /opendata/latency/latest/pairs/jnb-mow.pings.{csv,json,yaml}. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Johannesburg → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0".

Round published August 16, 2026. See the full interactive latency matrix or browse more city-pair routes.

Johannesburg, South Africa → Moscow, Russia RTT