Seattle to Johannesburg ping and RTT: 282.7 ms, 4.69 ms jitter, 161.61 ms fiber floor, and 57.2% efficiency across AS203314. Updated 2026-08-10.

🇺🇸 This page compares the published ping and round-trip time (RTT) from Seattle (SEA) to 🇿🇦 Johannesburg (JNB) with vacuum and optical-fiber physical limits.

As of August 10, 2026, the Seattle → Johannesburg route on Hats Network averages 282.7 ms RTT across a 50-sample daily ICMP echo measurement round, 1.75× the theoretical fiber-floor limit of 161.61 ms.

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

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

Latency Summary

Metric	Value
RTT	282.7 ms
Jitter	4.69 ms
Packet Loss	0%
Standard Fiber Floor	161.61 ms
Fiber Efficiency	57.2%
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: SEA → JNB

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

Sample distribution: box = interquartile range (278.0–288.1 ms), median 280.5 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 (161.6 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	277.54
2	100	287.07
3	200	288.02
4	300	291.30
5	400	290.66
6	500	288.14
7	600	282.62
8	700	279.60
9	800	295.43
10	900	288.87
11	1000	280.47
12	1100	280.16
13	1200	277.89
14	1300	278.36
15	1400	276.06
16	1500	274.28
17	1600	282.86
18	1700	277.58
19	1800	278.86
20	1900	279.53
21	2000	291.26
22	2100	291.14
23	2200	287.25
24	2300	281.54
25	2400	280.48
26	2500	276.37
27	2600	276.42
28	2700	283.45
29	2800	291.03
30	2900	288.16
31	3000	280.25
32	3100	291.56
33	3200	280.28
34	3300	278.62
35	3400	293.47
36	3500	283.42
37	3600	279.45
38	3700	277.65
39	3800	276.59
40	3900	274.65
41	4000	274.40
42	4100	278.30
43	4200	278.00
44	4300	277.96
45	4400	280.97
46	4500	278.08
47	4600	285.35
48	4700	291.27
49	4800	282.26
50	4900	290.07

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 Seattle (47.60621, -122.33207) and Johannesburg (-26.20227, 28.04363). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	16,502.7 km
Vacuum RTT floor	110.09 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	161.61 ms
Low-latency fiber material floor	160.96 ms
Engineering floor (5% path allowance)	169.71 ms
Research 1.33× mapped-fiber reference	214.94 ms
Estimated unamplified path loss	3465.6 dB
Transparent optical spans / inline amplifiers	217 / 216
Published RTT inflation over fiber floor	1.75×

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	274.28 ms
Average RTT	282.7 ms
Maximum RTT	295.43 ms
Standard deviation	5.79 ms
Stdev / average	2.0%

RTT trend

Estimated route stability across the selected time window.

Average: 282.3 ms
Minimum: 279.8 ms
Maximum: 285.6 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Johannesburg to Seattle latency and RTT — 280.3 ms

Fastest routes departing Seattle (SEA)

Seattle to Los Angeles latency and RTT — 27.5 ms
Seattle to New York latency and RTT — 58.8 ms
Seattle to Ashburn latency and RTT — 62.3 ms
Seattle to Tokyo latency and RTT — 84 ms
Seattle to Miami latency and RTT — 88.1 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

Same corridor (North America → Africa)

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

Seattle to Johannesburg Latency, Ping & RTT | AS203314