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

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

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

Among the 19 measured routes departing São Paulo, this route ranks 19th fastest by average RTT.

With a stdev-to-average ratio of 2.2%, this route is more stable than the network median of 3.1%. Across the round, per-probe RTT ranged from 325.13 ms to 356.59 ms with a standard deviation of 7.33 ms.

Latency Summary

Metric	Value
RTT	333.4 ms
Jitter	7.12 ms
Packet Loss	0%
Standard Fiber Floor	72.88 ms
Fiber Efficiency	21.9%
Latency Tier	High
Source Region	South America
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: GRU → JNB

50 ICMP echo samples at 100 ms intervals · round 2026-08-10 · avg 333.4 ± 1.04 ms (SE)

Sample distribution: box = interquartile range (328.4–335.1 ms), median 331.3 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	343.96
2	100	335.25
3	200	337.32
4	300	328.65
5	400	330.87
6	500	330.09
7	600	328.20
8	700	325.85
9	800	334.84
10	900	345.04
11	1000	331.37
12	1100	336.07
13	1200	331.51
14	1300	328.30
15	1400	328.11
16	1500	356.59
17	1600	336.41
18	1700	332.02
19	1800	333.37
20	1900	327.66
21	2000	333.35
22	2100	348.68
23	2200	332.32
24	2300	328.03
25	2400	325.13
26	2500	332.05
27	2600	354.70
28	2700	336.62
29	2800	331.13
30	2900	331.53
31	3000	326.88
32	3100	333.52
33	3200	327.20
34	3300	345.35
35	3400	340.52
36	3500	330.00
37	3600	331.55
38	3700	330.85
39	3800	328.57
40	3900	330.09
41	4000	327.91
42	4100	349.85
43	4200	334.53
44	4300	328.91
45	4400	329.95
46	4500	326.70
47	4600	330.92
48	4700	326.10
49	4800	326.60
50	4900	328.98

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 São Paulo (-23.54750, -46.63611) and Johannesburg (-26.20227, 28.04363). 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.57×

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	325.13 ms
Average RTT	333.4 ms
Maximum RTT	356.59 ms
Standard deviation	7.33 ms
Stdev / average	2.2%

RTT trend

Estimated route stability across the selected time window.

Average: 333.3 ms
Minimum: 330.2 ms
Maximum: 336.0 ms
Average loss: 0.01%

Route Context

Departure PoP: São Paulo (GRU)
Destination PoP: Johannesburg (JNB)
Region overview: South America → Africa
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Johannesburg to São Paulo latency and RTT — 329.7 ms

Fastest routes departing São Paulo (GRU)

São Paulo to Miami latency and RTT — 74 ms
São Paulo to New York latency and RTT — 122 ms
São Paulo to Ashburn latency and RTT — 128 ms
São Paulo to Los Angeles latency and RTT — 159.2 ms
São Paulo to Seattle latency and RTT — 160.9 ms

Fastest routes arriving at Johannesburg (JNB)

Amsterdam to Johannesburg latency and RTT — 171.9 ms
Berlin to Johannesburg latency and RTT — 172.1 ms
London to Johannesburg latency and RTT — 179.8 ms
Paris to Johannesburg latency and RTT — 180.9 ms
Frankfurt to Johannesburg latency and RTT — 188.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/gru-jnb.pings.{csv,json,yaml}. When citing, include the route, the measurement round date, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Johannesburg 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.

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