ICMP RTT measurements between Moscow, Russia and Johannesburg, South Africa: average latency, jitter, packet loss, and route efficiency for the round.

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

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

During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Johannesburg produced an average RTT of 201.9 ms, with a minimum of 192.01 ms and a maximum of 232.17 ms. The route recorded 0% packet loss and a jitter of 7.49 ms.

For a geodesic distance of 9,125.7 km, the vacuum floor is 60.88 ms and the fiber floor is 89.37 ms. At 201.9 ms, the average is 2.26 times the fiber floor, corresponding to a fiber-floor efficiency of 44.3%.

This route ranked 16th among the 19 routes measured in the round, placing it near the higher-latency end of the set. Its standard deviation of 7.94 ms is about 3.9% of the mean, above the 3.28% median standard-deviation-to-average ratio for the round. Despite the higher average and wider spread, every probe was returned without loss, indicating the route remained fully available across the entire measurement window.

Latency Summary

Metric	Value
RTT	201.9 ms
Jitter	7.49 ms
Packet Loss	0%
Standard Fiber Floor	89.37 ms
Fiber Efficiency	44.3%
Latency Tier	Fair
Source Region	Europe
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: MOW → JNB

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

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

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	209.30
2	100	200.91
3	200	194.09
4	300	199.73
5	400	208.10
6	500	206.29
7	600	202.47
8	700	202.62
9	800	194.79
10	900	192.01
11	1000	193.51
12	1100	193.73
13	1200	192.48
14	1300	226.74
15	1400	208.67
16	1500	232.17
17	1600	205.84
18	1700	195.74
19	1800	192.24
20	1900	193.62
21	2000	203.49
22	2100	198.23
23	2200	193.37
24	2300	205.07
25	2400	204.67
26	2500	199.24
27	2600	213.24
28	2700	198.37
29	2800	212.74
30	2900	198.66
31	3000	213.19
32	3100	198.67
33	3200	202.60
34	3300	196.19
35	3400	201.56
36	3500	198.73
37	3600	201.77
38	3700	208.09
39	3800	204.78
40	3900	196.48
41	4000	197.37
42	4100	195.59
43	4200	202.18
44	4300	201.99
45	4400	204.01
46	4500	205.40
47	4600	195.84
48	4700	197.59
49	4800	204.12
50	4900	196.72

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 Moscow (55.75204, 37.61781) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.

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

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	192.01 ms
Average RTT	201.9 ms
Maximum RTT	232.17 ms
Standard deviation	7.94 ms
Stdev / average	3.9%

RTT trend

Estimated route stability across the selected time window.

Average: 202.1 ms
Minimum: 199.7 ms
Maximum: 204.1 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Johannesburg to Moscow latency and RTT — 200.7 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27.5 ms
Moscow to Frankfurt latency and RTT — 35.9 ms
Moscow to Amsterdam latency and RTT — 37.6 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 44 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 (Europe → Africa)

Marseille to Johannesburg latency and RTT — 198.5 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/mow-jnb.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → 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.

Moscow, Russia → Johannesburg, South Africa RTT