Johannesburg, South Africa → Frankfurt, Germany RTT
Measured ICMP RTT from Johannesburg, South Africa to Frankfurt, Germany: average, jitter, packet loss and rank from the 2026-08-16 round.
🇿🇦 Johannesburg, South Africa (JNB) → 🇩🇪 Frankfurt, Germany (FRA)
Measurement round: 2026-08-16T04:07:28Z.
In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Johannesburg to Frankfurt averaged 166 ms, with a minimum of 156.26 ms, a maximum of 186.26 ms and zero packet loss across all 50 samples.
The standard deviation was 7.97 ms and jitter was 7.73 ms, so the route showed a fairly consistent profile despite a roughly 30 ms range between its fastest and slowest replies. That standard deviation is about 4.8% of the average, above the 3.28% median stdev-to-average ratio seen across the 19 outbound routes in the same measurement set.
This route ranked 4th among those 19 routes. Its 166 ms average is 1.96 times the theoretical fiber-floor minimum for the 8,666.9 km great-circle distance, placing fiber efficiency at 51.1%; in practical terms, the path remains well above the optical floor, but the zero-loss sample and modest jitter make the route a stable reference for Johannesburg-to-Frankfurt connectivity.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 166 ms |
| Jitter | 7.73 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 84.87 ms |
| Fiber Efficiency | 51.1% |
| 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 → FRA
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 166.0 ± 1.13 ms (SE)
Sample distribution: box = interquartile range (159.4–169.6 ms), median 164.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 (84.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 159.20 |
| 2 | 100 | 159.01 |
| 3 | 200 | 156.70 |
| 4 | 300 | 164.13 |
| 5 | 400 | 176.66 |
| 6 | 500 | 162.78 |
| 7 | 600 | 184.47 |
| 8 | 700 | 166.95 |
| 9 | 800 | 159.57 |
| 10 | 900 | 180.33 |
| 11 | 1000 | 177.95 |
| 12 | 1100 | 165.39 |
| 13 | 1200 | 159.44 |
| 14 | 1300 | 157.41 |
| 15 | 1400 | 161.33 |
| 16 | 1500 | 162.50 |
| 17 | 1600 | 177.22 |
| 18 | 1700 | 163.88 |
| 19 | 1800 | 161.49 |
| 20 | 1900 | 170.14 |
| 21 | 2000 | 166.73 |
| 22 | 2100 | 164.76 |
| 23 | 2200 | 158.50 |
| 24 | 2300 | 156.31 |
| 25 | 2400 | 158.58 |
| 26 | 2500 | 157.54 |
| 27 | 2600 | 156.66 |
| 28 | 2700 | 156.26 |
| 29 | 2800 | 177.26 |
| 30 | 2900 | 168.17 |
| 31 | 3000 | 164.84 |
| 32 | 3100 | 158.63 |
| 33 | 3200 | 163.57 |
| 34 | 3300 | 186.26 |
| 35 | 3400 | 168.10 |
| 36 | 3500 | 170.69 |
| 37 | 3600 | 180.36 |
| 38 | 3700 | 166.25 |
| 39 | 3800 | 179.95 |
| 40 | 3900 | 172.63 |
| 41 | 4000 | 166.87 |
| 42 | 4100 | 175.97 |
| 43 | 4200 | 164.80 |
| 44 | 4300 | 160.23 |
| 45 | 4400 | 165.02 |
| 46 | 4500 | 165.86 |
| 47 | 4600 | 159.46 |
| 48 | 4700 | 157.41 |
| 49 | 4800 | 165.08 |
| 50 | 4900 | 160.70 |
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 Frankfurt am Main (50.11552, 8.68417). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 8,666.9 km |
| Vacuum RTT floor | 57.82 ms |
| Standard fiber RTT floor () | 84.87 ms |
| Low-latency fiber material floor | 84.53 ms |
| Engineering floor (5% path allowance) | 89.13 ms |
| Research 1.33× mapped-fiber reference | 112.88 ms |
| Estimated unamplified path loss | 1820.1 dB |
| Transparent optical spans / inline amplifiers | 114 / 113 |
| Published RTT inflation over fiber floor | 1.96× |
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 | 156.26 ms |
| Average RTT | 166 ms |
| Maximum RTT | 186.26 ms |
| Standard deviation | 7.97 ms |
| Stdev / average | 4.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 166.0 ms
- Minimum
- 164.3 ms
- Maximum
- 167.5 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Johannesburg (JNB)
- Destination PoP: Frankfurt (FRA)
- Region overview: Africa → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Frankfurt to Johannesburg latency and RTT — 188.4 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 Marseille latency and RTT — 172 ms
- Johannesburg to Berlin latency and RTT — 172.1 ms
Fastest routes arriving at Frankfurt (FRA)
- Amsterdam to Frankfurt latency and RTT — 5.9 ms
- Berlin to Frankfurt latency and RTT — 6.1 ms
- Paris to Frankfurt latency and RTT — 7.6 ms
- London to Frankfurt latency and RTT — 13.6 ms
- Marseille to Frankfurt latency and RTT — 16 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-fra.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Frankfurt 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.