Berlin to Johannesburg ping and RTT: 172.1 ms, 2.85 ms jitter, 86.53 ms fiber floor, and 50.3% efficiency across AS203314. Updated 2026-08-10.

🇩🇪 This page compares the published ping and round-trip time (RTT) from Berlin (BER) to 🇿🇦 Johannesburg (JNB) with vacuum and optical-fiber physical limits.

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

Among the 19 measured routes departing Berlin, this route ranks 15th fastest by average RTT.

With a stdev-to-average ratio of 2.1%, this route is more stable than the network median of 3.1%. Across the round, per-probe RTT ranged from 168.43 ms to 190.03 ms with a standard deviation of 3.66 ms.

Latency Summary

Metric	Value
RTT	172.1 ms
Jitter	2.85 ms
Packet Loss	0%
Standard Fiber Floor	86.53 ms
Fiber Efficiency	50.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: BER → JNB

50 ICMP echo samples at 100 ms intervals · round 2026-08-10 · avg 172.1 ± 0.52 ms (SE)

Sample distribution: box = interquartile range (169.9–172.9 ms), median 171.3 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 (86.5 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	168.94
2	100	190.03
3	200	177.20
4	300	172.18
5	400	170.79
6	500	170.71
7	600	168.92
8	700	170.96
9	800	169.72
10	900	169.93
11	1000	169.71
12	1100	168.63
13	1200	171.29
14	1300	176.18
15	1400	171.35
16	1500	173.56
17	1600	173.10
18	1700	170.25
19	1800	170.21
20	1900	172.14
21	2000	177.33
22	2100	171.91
23	2200	174.38
24	2300	172.45
25	2400	171.46
26	2500	173.05
27	2600	177.82
28	2700	172.98
29	2800	170.05
30	2900	168.68
31	3000	168.82
32	3100	170.95
33	3200	169.28
34	3300	168.67
35	3400	168.43
36	3500	169.97
37	3600	170.55
38	3700	169.21
39	3800	172.38
40	3900	170.64
41	4000	169.32
42	4100	180.05
43	4200	175.93
44	4300	172.76
45	4400	174.12
46	4500	171.96
47	4600	172.34
48	4700	171.36
49	4800	170.01
50	4900	172.34

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 Berlin (52.52437, 13.41053) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,836.6 km
Vacuum RTT floor	58.95 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	86.53 ms
Low-latency fiber material floor	86.19 ms
Engineering floor (5% path allowance)	90.87 ms
Research 1.33× mapped-fiber reference	115.09 ms
Estimated unamplified path loss	1855.7 dB
Transparent optical spans / inline amplifiers	116 / 115
Published RTT inflation over fiber floor	1.99×

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	168.43 ms
Average RTT	172.1 ms
Maximum RTT	190.03 ms
Standard deviation	3.66 ms
Stdev / average	2.1%

RTT trend

Estimated route stability across the selected time window.

Average: 172.3 ms
Minimum: 170.6 ms
Maximum: 174.0 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Johannesburg to Berlin latency and RTT — 172.1 ms

Fastest routes departing Berlin (BER)

Berlin to Frankfurt latency and RTT — 6.1 ms
Berlin to Amsterdam latency and RTT — 7.2 ms
Berlin to Paris latency and RTT — 13.9 ms
Berlin to London latency and RTT — 15.8 ms
Berlin to Marseille latency and RTT — 20.7 ms

Fastest routes arriving at Johannesburg (JNB)

Amsterdam to Johannesburg latency and RTT — 171.9 ms
London to Johannesburg latency and RTT — 179.8 ms
Paris to Johannesburg latency and RTT — 180.9 ms
Frankfurt to Johannesburg latency and RTT — 188.9 ms
Marseille to Johannesburg latency and RTT — 198.9 ms

Same corridor (Europe → Africa)

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

Berlin to Johannesburg Latency, Ping & RTT | AS203314