Berlin, Germany → Johannesburg, South Africa RTT
ICMP echo RTT measurements from Berlin, Germany to Johannesburg, South Africa: average latency, jitter, packet loss, and route efficiency for 2026-08-16 round.
🇩🇪 Berlin, Germany (BER) → 🇿🇦 Johannesburg, South Africa (JNB)
Measurement round: 2026-08-16T04:07:28Z.
For the 2026-08-16T04:07:28Z round, ICMP echo probes from Berlin, Germany to Johannesburg, South Africa averaged 172.1 ms over 50 samples at 100 ms intervals, with a minimum of 163.72 ms, a maximum of 199.65 ms, and no packet loss.
Against an 8,836.6 km great-circle distance and a fiber-floor estimate of 86.53 ms, the measured RTT is 1.99 times the floor, yielding 50.3% fiber efficiency and a fair latency tier. The 7.34 ms standard deviation and 6.16 ms jitter show moderate probe-to-probe variation, with the maximum about 27.5 ms above the minimum.
Among the 19 outbound routes measured from Berlin, this route ranks 15th, placing it in the slower half of the set, and its standard deviation equals about 4.3% of the average, above the 3.28% median variability seen across the network's measured routes. Despite the wider spread, zero packet loss and a sub-200 ms maximum make the route consistent enough for round-trip trend checks.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 172.1 ms |
| Jitter | 6.16 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-16T04:07:28Z · avg 172.1 ± 1.04 ms (SE)
Sample distribution: box = interquartile range (166.7–177.1 ms), median 169.7 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.61 |
| 2 | 100 | 170.66 |
| 3 | 200 | 183.41 |
| 4 | 300 | 177.31 |
| 5 | 400 | 178.37 |
| 6 | 500 | 178.15 |
| 7 | 600 | 177.38 |
| 8 | 700 | 167.24 |
| 9 | 800 | 166.21 |
| 10 | 900 | 165.74 |
| 11 | 1000 | 177.38 |
| 12 | 1100 | 169.57 |
| 13 | 1200 | 192.47 |
| 14 | 1300 | 178.38 |
| 15 | 1400 | 168.88 |
| 16 | 1500 | 176.33 |
| 17 | 1600 | 171.31 |
| 18 | 1700 | 167.89 |
| 19 | 1800 | 166.19 |
| 20 | 1900 | 172.41 |
| 21 | 2000 | 167.47 |
| 22 | 2100 | 164.82 |
| 23 | 2200 | 171.36 |
| 24 | 2300 | 177.67 |
| 25 | 2400 | 171.36 |
| 26 | 2500 | 169.31 |
| 27 | 2600 | 168.79 |
| 28 | 2700 | 169.59 |
| 29 | 2800 | 199.65 |
| 30 | 2900 | 181.79 |
| 31 | 3000 | 169.06 |
| 32 | 3100 | 170.16 |
| 33 | 3200 | 169.89 |
| 34 | 3300 | 170.98 |
| 35 | 3400 | 167.03 |
| 36 | 3500 | 165.39 |
| 37 | 3600 | 163.72 |
| 38 | 3700 | 166.61 |
| 39 | 3800 | 180.20 |
| 40 | 3900 | 173.61 |
| 41 | 4000 | 170.75 |
| 42 | 4100 | 165.03 |
| 43 | 4200 | 164.36 |
| 44 | 4300 | 175.98 |
| 45 | 4400 | 167.92 |
| 46 | 4500 | 165.67 |
| 47 | 4600 | 166.23 |
| 48 | 4700 | 165.55 |
| 49 | 4800 | 165.95 |
| 50 | 4900 | 186.21 |
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 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 () | 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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 163.72 ms |
| Average RTT | 172.1 ms |
| Maximum RTT | 199.65 ms |
| Standard deviation | 7.34 ms |
| Stdev / average | 4.3% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 172.1 ms
- Minimum
- 170.3 ms
- Maximum
- 173.4 ms
- Average loss
- 0.03%
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
Related City-Pair Routes
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 London latency and RTT — 15.2 ms
- Berlin to Paris latency and RTT — 15.6 ms
- Berlin to Marseille latency and RTT — 20.2 ms
Fastest routes arriving at Johannesburg (JNB)
- Amsterdam to Johannesburg latency and RTT — 171.9 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
- Marseille to Johannesburg latency and RTT — 198.5 ms
Same corridor (Europe → Africa)
- Moscow to Johannesburg latency and RTT — 201.9 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 timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → 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.