ICMP RTT measurement from Miami, USA to Johannesburg, South Africa: average 259.8 ms, min/max latency, jitter, packet loss, and route efficiency.

🇺🇸 Miami, USA (MIA) → 🇿🇦 Johannesburg, South Africa (JNB)

Measurement round: 2026-08-16T04:07:28Z.

The 2026-08-16T04:07:28Z ICMP echo RTT run from Miami, USA to Johannesburg, South Africa averaged 259.8 ms over 50 samples, with a minimum of 252.44 ms and a maximum of 277.9 ms. Zero packet loss, a 6.11 ms standard deviation, and 5.21 ms jitter show that the high-latency classification is driven by distance rather than instability.

At a geodesic distance of 12,945.8 km, the theoretical fiber-floor RTT is 126.78 ms. The observed average is 2.05x that floor, which corresponds to a fiber efficiency of 48.8% — in other words, the measured path uses about 49% of the theoretical optical speed limit.

This route ranked 19th of 19 outbound routes in the network's measurement set. Its standard deviation relative to average RTT was 2.35%, below the 3.28% median across that set, so even at 259.8 ms the connection is more predictable than its rank might suggest.

Latency Summary

Metric	Value
RTT	259.8 ms
Jitter	5.21 ms
Packet Loss	0%
Standard Fiber Floor	126.78 ms
Fiber Efficiency	48.8%
Latency Tier	High
Source Region	North 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: MIA → JNB

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 259.8 ± 0.86 ms (SE)

Sample distribution: box = interquartile range (255.6–261.7 ms), median 258.2 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 (126.8 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	260.71
2	100	257.88
3	200	262.04
4	300	255.38
5	400	256.00
6	500	254.25
7	600	277.90
8	700	262.31
9	800	262.57
10	900	271.98
11	1000	258.83
12	1100	254.54
13	1200	273.03
14	1300	264.43
15	1400	258.23
16	1500	260.03
17	1600	256.77
18	1700	255.10
19	1800	259.48
20	1900	259.64
21	2000	259.14
22	2100	256.96
23	2200	255.88
24	2300	255.10
25	2400	255.72
26	2500	254.28
27	2600	252.51
28	2700	255.74
29	2800	253.79
30	2900	252.44
31	3000	254.60
32	3100	257.42
33	3200	259.95
34	3300	257.62
35	3400	253.60
36	3500	255.48
37	3600	266.08
38	3700	258.62
39	3800	255.52
40	3900	258.21
41	4000	259.77
42	4100	261.05
43	4200	257.31
44	4300	269.21
45	4400	273.81
46	4500	261.91
47	4600	259.28
48	4700	256.30
49	4800	277.11
50	4900	264.49

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 Miami (25.77427, -80.19366) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	12,945.8 km
Vacuum RTT floor	86.36 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	126.78 ms
Low-latency fiber material floor	126.27 ms
Engineering floor (5% path allowance)	133.13 ms
Research 1.33× mapped-fiber reference	168.61 ms
Estimated unamplified path loss	2718.6 dB
Transparent optical spans / inline amplifiers	170 / 169
Published RTT inflation over fiber floor	2.05×

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	252.44 ms
Average RTT	259.8 ms
Maximum RTT	277.9 ms
Standard deviation	6.11 ms
Stdev / average	2.4%

RTT trend

Estimated route stability across the selected time window.

Average: 260.1 ms
Minimum: 257.8 ms
Maximum: 262.1 ms
Average loss: 0.04%

Route Context

Departure PoP: Miami (MIA)
Destination PoP: Johannesburg (JNB)
Region overview: North America → Africa
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Johannesburg to Miami latency and RTT — 259.9 ms

Fastest routes departing Miami (MIA)

Miami to Ashburn latency and RTT — 27.3 ms
Miami to New York latency and RTT — 33.3 ms
Miami to Los Angeles latency and RTT — 56.8 ms
Miami to Seattle latency and RTT — 81.9 ms
Miami to London latency and RTT — 101.8 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.6 ms
Paris to Johannesburg latency and RTT — 180.9 ms
Frankfurt to Johannesburg latency and RTT — 188.4 ms

Same corridor (North America → Africa)

New York to Johannesburg latency and RTT — 221.5 ms
Ashburn to Johannesburg latency and RTT — 228.3 ms
Seattle to Johannesburg latency and RTT — 282.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/mia-jnb.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → 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.

Miami, USA → Johannesburg, South Africa RTT