Johannesburg, South Africa → São Paulo, Brazil RTT
ICMP RTT from Johannesburg, South Africa to São Paulo, Brazil: average 328.7 ms, zero packet loss, stability and path-efficiency data for this route.
🇿🇦 Johannesburg, South Africa (JNB) → 🇧🇷 São Paulo, Brazil (GRU)
Measurement round: 2026-08-16T04:07:28Z.
In round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Johannesburg, South Africa to São Paulo, Brazil produced an average RTT of 328.7 ms, with a minimum of 319.02 ms and a maximum of 366.86 ms. Packet loss was zero percent across the entire sample.
The straight-line distance between Johannesburg and São Paulo is only 7,441.9 km, giving a vacuum round-trip floor of 49.65 ms and a direct fiber floor of 72.88 ms. At 328.7 ms, the measured route is 4.51 times higher than that fiber floor and achieves just 22.2 percent fiber efficiency, indicating that the actual network path is substantially longer than the map distance suggests.
Among the 19 outbound routes in this measurement set, the Johannesburg–São Paulo leg ranks 15th by average RTT, placing it in the slower tail. Its standard deviation of 9.87 ms is only about 3.00 percent of the average, however, and jitter was 7.53 ms, so the path, while slow, is very consistent. The observed variability is below the 3.28 percent median seen across the network.
The practical takeaway is that 328.7 ms is not an anomaly from a few bad probes: the entire 50-sample range stays between 319.02 ms and 366.86 ms. This stable, high-latency band can be treated as the route's normal ICMP behavior for this measurement round.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 328.7 ms |
| Jitter | 7.53 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 72.88 ms |
| Fiber Efficiency | 22.2% |
| Latency Tier | High |
| Source Region | Africa |
| Destination Region | South America |
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 → GRU
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 328.7 ± 1.40 ms (SE)
Sample distribution: box = interquartile range (322.5–329.2 ms), median 325.9 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 (72.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 325.74 |
| 2 | 100 | 324.93 |
| 3 | 200 | 330.82 |
| 4 | 300 | 326.06 |
| 5 | 400 | 338.45 |
| 6 | 500 | 328.98 |
| 7 | 600 | 326.05 |
| 8 | 700 | 320.88 |
| 9 | 800 | 321.39 |
| 10 | 900 | 323.95 |
| 11 | 1000 | 322.33 |
| 12 | 1100 | 325.96 |
| 13 | 1200 | 322.25 |
| 14 | 1300 | 327.27 |
| 15 | 1400 | 335.87 |
| 16 | 1500 | 326.93 |
| 17 | 1600 | 321.35 |
| 18 | 1700 | 319.03 |
| 19 | 1800 | 329.24 |
| 20 | 1900 | 328.64 |
| 21 | 2000 | 325.69 |
| 22 | 2100 | 327.76 |
| 23 | 2200 | 323.74 |
| 24 | 2300 | 319.93 |
| 25 | 2400 | 319.02 |
| 26 | 2500 | 361.94 |
| 27 | 2600 | 337.45 |
| 28 | 2700 | 366.86 |
| 29 | 2800 | 342.35 |
| 30 | 2900 | 326.53 |
| 31 | 3000 | 321.04 |
| 32 | 3100 | 350.37 |
| 33 | 3200 | 342.12 |
| 34 | 3300 | 339.51 |
| 35 | 3400 | 326.57 |
| 36 | 3500 | 324.62 |
| 37 | 3600 | 321.15 |
| 38 | 3700 | 325.91 |
| 39 | 3800 | 326.66 |
| 40 | 3900 | 322.92 |
| 41 | 4000 | 321.77 |
| 42 | 4100 | 337.52 |
| 43 | 4200 | 325.56 |
| 44 | 4300 | 324.34 |
| 45 | 4400 | 321.76 |
| 46 | 4500 | 320.24 |
| 47 | 4600 | 324.40 |
| 48 | 4700 | 327.88 |
| 49 | 4800 | 329.80 |
| 50 | 4900 | 323.47 |
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 São Paulo (-23.54750, -46.63611). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 7,441.9 km |
| Vacuum RTT floor | 49.65 ms |
| Standard fiber RTT floor () | 72.88 ms |
| Low-latency fiber material floor | 72.58 ms |
| Engineering floor (5% path allowance) | 76.53 ms |
| Research 1.33× mapped-fiber reference | 96.93 ms |
| Estimated unamplified path loss | 1562.8 dB |
| Transparent optical spans / inline amplifiers | 98 / 97 |
| Published RTT inflation over fiber floor | 4.51× |
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 | 319.02 ms |
| Average RTT | 328.7 ms |
| Maximum RTT | 366.86 ms |
| Standard deviation | 9.87 ms |
| Stdev / average | 3.0% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 328.7 ms
- Minimum
- 325.0 ms
- Maximum
- 331.6 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Johannesburg (JNB)
- Destination PoP: São Paulo (GRU)
- Region overview: Africa → South America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- São Paulo to Johannesburg latency and RTT — 333.8 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 São Paulo (GRU)
- Ashburn to São Paulo latency and RTT — 101.4 ms
- New York to São Paulo latency and RTT — 106.9 ms
- Miami to São Paulo latency and RTT — 128.7 ms
- Los Angeles to São Paulo latency and RTT — 131.3 ms
- Seattle to São Paulo latency and RTT — 155.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-gru.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → São Paulo 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.