ICMP echo RTT measurements from Johannesburg, South Africa to Amsterdam, Netherlands: average latency, loss, jitter, and stability for the Europe route.

🇿🇦 Johannesburg, South Africa (JNB) → 🇳🇱 Amsterdam, Netherlands (AMS)

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

The Johannesburg–Amsterdam path produced a 163.2 ms average ICMP echo RTT across 50 samples at 100 ms intervals, with samples ranging from 158.68 ms to 177.43 ms and no packet loss. The 4.23 ms standard deviation and 3.46 ms jitter indicate a comparatively stable fair-latency route.

For the 2026-08-16T04:07:28Z round, this route ranks second in a 19-route outbound set, and its standard deviation works out to about 2.59% of the average, below the 3.28% median ratio for the set. The 8,991.8 km great-circle distance has a line-of-sight speed-of-light floor of 59.99 ms and a fiber-floor reference of 88.05 ms.

With an RTT only 1.85 times the fiber-floor reference, the route reaches 54% fiber efficiency, indicating that the measured latency leaves relatively little headroom over the physical reference. Low loss, low jitter, and a top-two outbound position make this one of the steadier long-haul measurements in the round.

Latency Summary

Metric	Value
RTT	163.2 ms
Jitter	3.46 ms
Packet Loss	0%
Standard Fiber Floor	88.05 ms
Fiber Efficiency	54%
Latency Tier	Fair
Source Region	Africa
Destination Region	Europe

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 → AMS

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

Sample distribution: box = interquartile range (160.6–164.5 ms), median 161.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 (88.0 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	161.49
2	100	159.23
3	200	161.93
4	300	162.29
5	400	160.61
6	500	161.99
7	600	162.02
8	700	163.33
9	800	161.56
10	900	177.43
11	1000	164.81
12	1100	175.54
13	1200	164.21
14	1300	160.08
15	1400	158.90
16	1500	158.68
17	1600	161.07
18	1700	160.09
19	1800	160.61
20	1900	165.43
21	2000	174.14
22	2100	168.29
23	2200	163.65
24	2300	167.60
25	2400	162.78
26	2500	161.86
27	2600	165.58
28	2700	173.04
29	2800	164.04
30	2900	165.86
31	3000	160.99
32	3100	161.74
33	3200	161.50
34	3300	160.31
35	3400	158.71
36	3500	160.21
37	3600	159.57
38	3700	163.37
39	3800	162.40
40	3900	159.38
41	4000	160.84
42	4100	164.31
43	4200	161.24
44	4300	160.67
45	4400	164.51
46	4500	167.09
47	4600	165.53
48	4700	161.30
49	4800	158.87
50	4900	159.32

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 Amsterdam (52.37403, 4.88969). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,991.8 km
Vacuum RTT floor	59.99 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	88.05 ms
Low-latency fiber material floor	87.7 ms
Engineering floor (5% path allowance)	92.47 ms
Research 1.33× mapped-fiber reference	117.11 ms
Estimated unamplified path loss	1888.3 dB
Transparent optical spans / inline amplifiers	119 / 118
Published RTT inflation over fiber floor	1.85×

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	158.68 ms
Average RTT	163.2 ms
Maximum RTT	177.43 ms
Standard deviation	4.23 ms
Stdev / average	2.6%

RTT trend

Estimated route stability across the selected time window.

Average: 163.1 ms
Minimum: 161.6 ms
Maximum: 164.6 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Amsterdam to Johannesburg latency and RTT — 171.9 ms

Fastest routes departing Johannesburg (JNB)

Johannesburg to London latency and RTT — 158 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
Johannesburg to Berlin latency and RTT — 172.1 ms

Fastest routes arriving at Amsterdam (AMS)

London to Amsterdam latency and RTT — 5.2 ms
Frankfurt to Amsterdam latency and RTT — 5.9 ms
Paris to Amsterdam latency and RTT — 7 ms
Berlin to Amsterdam latency and RTT — 7.2 ms
Marseille to Amsterdam latency and RTT — 20.3 ms

Same corridor (Africa → Europe)

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