Johannesburg to São Paulo ping and RTT: 329.7 ms, 9.43 ms jitter, 72.88 ms fiber floor, and 22.1% efficiency across AS203314. Updated 2026-08-10.

🇿🇦 This page compares the published ping and round-trip time (RTT) from Johannesburg (JNB) to 🇧🇷 São Paulo (GRU) with vacuum and optical-fiber physical limits.

As of August 10, 2026, the Johannesburg → São Paulo route on Hats Network averages 329.7 ms RTT across a 50-sample daily ICMP echo measurement round, 4.52× the theoretical fiber-floor limit of 72.88 ms.

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

With a stdev-to-average ratio of 3.2%, this route sits close to the network-wide stability median of 3.1%. Across the round, per-probe RTT ranged from 316.85 ms to 366.36 ms with a standard deviation of 10.65 ms.

Latency Summary

Metric	Value
RTT	329.7 ms
Jitter	9.43 ms
Packet Loss	0%
Standard Fiber Floor	72.88 ms
Fiber Efficiency	22.1%
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-10 · avg 329.7 ± 1.51 ms (SE)

Sample distribution: box = interquartile range (321.6–333.9 ms), median 327.1 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	316.85
2	100	338.87
3	200	332.09
4	300	359.49
5	400	342.70
6	500	328.54
7	600	327.13
8	700	324.00
9	800	319.91
10	900	338.10
11	1000	331.19
12	1100	322.58
13	1200	319.19
14	1300	326.87
15	1400	327.13
16	1500	321.56
17	1600	317.73
18	1700	317.79
19	1800	321.54
20	1900	334.11
21	2000	344.12
22	2100	348.35
23	2200	366.36
24	2300	333.08
25	2400	321.26
26	2500	323.26
27	2600	326.70
28	2700	321.69
29	2800	338.55
30	2900	328.60
31	3000	325.04
32	3100	321.10
33	3200	330.14
34	3300	321.79
35	3400	327.52
36	3500	352.59
37	3600	331.99
38	3700	323.02
39	3800	334.96
40	3900	328.90
41	4000	337.33
42	4100	326.40
43	4200	321.29
44	4300	320.78
45	4400	330.51
46	4500	339.33
47	4600	323.56
48	4700	318.52
49	4800	319.02
50	4900	331.87

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 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 ( $n_g=1.4679$ )	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.52×

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	316.85 ms
Average RTT	329.7 ms
Maximum RTT	366.36 ms
Standard deviation	10.65 ms
Stdev / average	3.2%

RTT trend

Estimated route stability across the selected time window.

Average: 329.9 ms
Minimum: 326.0 ms
Maximum: 333.1 ms
Average loss: 0.01%

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

Reverse direction

São Paulo to Johannesburg latency and RTT — 333.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 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 — 102.3 ms
New York to São Paulo latency and RTT — 108.1 ms
Miami to São Paulo latency and RTT — 129.2 ms
Los Angeles to São Paulo latency and RTT — 159.3 ms
Seattle to São Paulo latency and RTT — 162.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/jnb-gru.pings.{csv,json,yaml}. When citing, include the route, the measurement round date, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → São Paulo 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.

Johannesburg to São Paulo Latency, Ping & RTT | AS203314