Johannesburg to Berlin Latency, Ping & RTT | AS203314
Johannesburg to Berlin ping and RTT: 172.1 ms, 3.86 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 Johannesburg (JNB) to π©πͺ Berlin (BER) with vacuum and optical-fiber physical limits.
As of August 10, 2026, the Johannesburg β Berlin 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 Johannesburg, this route ranks 6th fastest by average RTT.
With a stdev-to-average ratio of 2.8%, this route sits close to the network-wide stability median of 3.1%. Across the round, per-probe RTT ranged from 166.97 ms to 195.41 ms with a standard deviation of 4.79 ms.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 172.1 ms |
| Jitter | 3.86 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 86.53 ms |
| Fiber Efficiency | 50.3% |
| 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 β BER
50 ICMP echo samples at 100 ms intervals Β· round 2026-08-10 Β· avg 172.1 Β± 0.68 ms (SE)
Sample distribution: box = interquartile range (169.7β173.1 ms), median 170.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 (86.5 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 167.86 |
| 2 | 100 | 167.90 |
| 3 | 200 | 166.97 |
| 4 | 300 | 168.14 |
| 5 | 400 | 173.36 |
| 6 | 500 | 172.58 |
| 7 | 600 | 170.82 |
| 8 | 700 | 170.52 |
| 9 | 800 | 185.46 |
| 10 | 900 | 172.72 |
| 11 | 1000 | 171.38 |
| 12 | 1100 | 168.11 |
| 13 | 1200 | 176.45 |
| 14 | 1300 | 170.43 |
| 15 | 1400 | 169.65 |
| 16 | 1500 | 167.78 |
| 17 | 1600 | 172.89 |
| 18 | 1700 | 174.85 |
| 19 | 1800 | 170.66 |
| 20 | 1900 | 173.72 |
| 21 | 2000 | 179.37 |
| 22 | 2100 | 177.55 |
| 23 | 2200 | 171.99 |
| 24 | 2300 | 168.17 |
| 25 | 2400 | 172.74 |
| 26 | 2500 | 172.90 |
| 27 | 2600 | 170.72 |
| 28 | 2700 | 167.63 |
| 29 | 2800 | 168.01 |
| 30 | 2900 | 172.72 |
| 31 | 3000 | 174.61 |
| 32 | 3100 | 171.79 |
| 33 | 3200 | 172.78 |
| 34 | 3300 | 177.38 |
| 35 | 3400 | 169.81 |
| 36 | 3500 | 167.76 |
| 37 | 3600 | 173.23 |
| 38 | 3700 | 170.48 |
| 39 | 3800 | 170.14 |
| 40 | 3900 | 167.27 |
| 41 | 4000 | 170.26 |
| 42 | 4100 | 174.14 |
| 43 | 4200 | 169.91 |
| 44 | 4300 | 171.88 |
| 45 | 4400 | 169.65 |
| 46 | 4500 | 170.09 |
| 47 | 4600 | 174.52 |
| 48 | 4700 | 170.71 |
| 49 | 4800 | 169.13 |
| 50 | 4900 | 195.41 |
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.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Johannesburg (-26.20227, 28.04363) and Berlin (52.52437, 13.41053). 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 () | 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 | 166.97 ms |
| Average RTT | 172.1 ms |
| Maximum RTT | 195.41 ms |
| Standard deviation | 4.79 ms |
| Stdev / average | 2.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 172.1 ms
- Minimum
- 171.0 ms
- Maximum
- 173.7 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Johannesburg (JNB)
- Destination PoP: Berlin (BER)
- Region overview: Africa β Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Berlin to Johannesburg latency and RTT β 172.1 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 Berlin (BER)
- Frankfurt to Berlin latency and RTT β 6.1 ms
- Amsterdam to Berlin latency and RTT β 7.2 ms
- Paris to Berlin latency and RTT β 14 ms
- London to Berlin latency and RTT β 16.4 ms
- Marseille to Berlin latency and RTT β 20.8 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-ber.pings.{csv,json,yaml}. When citing, include the route, the measurement round date, and the dataset version β for example: "Hats Network latency dataset, Johannesburg β Berlin 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.