Johannesburg to Amsterdam ping and RTT: 163.2 ms, 7.19 ms jitter, 88.05 ms fiber floor, and 54% efficiency across AS203314. Updated 2026-08-10.

🇿🇦 This page compares the published ping and round-trip time (RTT) from Johannesburg (JNB) to 🇳🇱 Amsterdam (AMS) with vacuum and optical-fiber physical limits.

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

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

With a stdev-to-average ratio of 4.8%, this route fluctuates more than the network median of 3.1%, so short congestion windows can surface as transient RTT spikes. Across the round, per-probe RTT ranged from 151.54 ms to 186.36 ms with a standard deviation of 7.89 ms.

Latency Summary

Metric	Value
RTT	163.2 ms
Jitter	7.19 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-10 · avg 163.2 ± 1.12 ms (SE)

Sample distribution: box = interquartile range (157.8–167.3 ms), median 161.8 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	162.77
2	100	157.41
3	200	162.17
4	300	160.00
5	400	164.81
6	500	174.86
7	600	166.58
8	700	159.34
9	800	162.83
10	900	156.53
11	1000	153.34
12	1100	161.22
13	1200	154.58
14	1300	175.52
15	1400	173.82
16	1500	158.92
17	1600	154.33
18	1700	153.42
19	1800	151.54
20	1900	168.05
21	2000	163.21
22	2100	163.76
23	2200	160.52
24	2300	154.01
25	2400	154.74
26	2500	161.86
27	2600	159.79
28	2700	167.57
29	2800	161.76
30	2900	156.92
31	3000	153.94
32	3100	151.94
33	3200	166.49
34	3300	161.11
35	3400	159.22
36	3500	175.15
37	3600	173.26
38	3700	160.33
39	3800	163.15
40	3900	178.80
41	4000	160.43
42	4100	168.47
43	4200	171.75
44	4300	174.50
45	4400	162.23
46	4500	186.36
47	4600	177.89
48	4700	165.53
49	4800	159.07
50	4900	154.20

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

Round Statistic	Value
Minimum RTT	151.54 ms
Average RTT	163.2 ms
Maximum RTT	186.36 ms
Standard deviation	7.89 ms
Stdev / average	4.8%

RTT trend

Estimated route stability across the selected time window.

Average: 163.2 ms
Minimum: 161.4 ms
Maximum: 164.7 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 — 19.3 ms

Same corridor (Africa → Europe)

Johannesburg to Moscow latency and RTT — 201.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 date, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Amsterdam 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 Amsterdam Latency, Ping & RTT | AS203314