Johannesburg, South Africa → New York, USA RTT
ICMP RTT data for the Johannesburg, South Africa, to New York, USA, route: average latency, jitter, loss, and efficiency for the 2026-08-16 round.
🇿🇦 Johannesburg, South Africa (JNB) → 🇺🇸 New York, USA (NYC)
Measurement round: 2026-08-16T04:07:28Z.
Round 2026-08-16T04:07:28Z captured ICMP echo RTT from Johannesburg, South Africa, to New York, USA, with 50 samples. Average RTT was 221.8 ms; the minimum was 213.14 ms and the maximum 261.72 ms, with zero packet loss, and the route was classified in the fair latency tier.
The geodesic distance is 12,832.9 km, giving a fiber floor of 125.67 ms. The measured average is about 1.76 times that floor, corresponding to a fiber efficiency of 56.7%, and the standard deviation and jitter are 8.43 ms and 6.44 ms, respectively.
This was one of 19 outbound routes from Johannesburg in the round, ranked 8th by average RTT. Variability at about 3.8% of the average is above the network-wide median of 3.28%, and the 48.58 ms gap between minimum and maximum suggests peak RTT values deserve attention on this route.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 221.8 ms |
| Jitter | 6.44 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 125.67 ms |
| Fiber Efficiency | 56.7% |
| Latency Tier | Fair |
| Source Region | Africa |
| Destination Region | North 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 → NYC
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 221.8 ± 1.19 ms (SE)
Sample distribution: box = interquartile range (215.5–225.1 ms), median 219.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 (125.7 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 231.27 |
| 2 | 100 | 230.54 |
| 3 | 200 | 219.42 |
| 4 | 300 | 214.85 |
| 5 | 400 | 213.57 |
| 6 | 500 | 217.77 |
| 7 | 600 | 213.93 |
| 8 | 700 | 226.21 |
| 9 | 800 | 218.90 |
| 10 | 900 | 213.27 |
| 11 | 1000 | 215.16 |
| 12 | 1100 | 213.96 |
| 13 | 1200 | 213.42 |
| 14 | 1300 | 213.14 |
| 15 | 1400 | 226.52 |
| 16 | 1500 | 217.28 |
| 17 | 1600 | 216.87 |
| 18 | 1700 | 223.12 |
| 19 | 1800 | 217.97 |
| 20 | 1900 | 217.93 |
| 21 | 2000 | 217.96 |
| 22 | 2100 | 214.24 |
| 23 | 2200 | 218.23 |
| 24 | 2300 | 215.11 |
| 25 | 2400 | 219.53 |
| 26 | 2500 | 221.53 |
| 27 | 2600 | 224.39 |
| 28 | 2700 | 221.37 |
| 29 | 2800 | 215.51 |
| 30 | 2900 | 229.51 |
| 31 | 3000 | 230.04 |
| 32 | 3100 | 225.17 |
| 33 | 3200 | 261.72 |
| 34 | 3300 | 231.70 |
| 35 | 3400 | 226.63 |
| 36 | 3500 | 224.47 |
| 37 | 3600 | 233.95 |
| 38 | 3700 | 219.04 |
| 39 | 3800 | 221.24 |
| 40 | 3900 | 214.22 |
| 41 | 4000 | 224.74 |
| 42 | 4100 | 225.93 |
| 43 | 4200 | 224.19 |
| 44 | 4300 | 240.15 |
| 45 | 4400 | 221.83 |
| 46 | 4500 | 224.56 |
| 47 | 4600 | 215.50 |
| 48 | 4700 | 219.15 |
| 49 | 4800 | 215.05 |
| 50 | 4900 | 218.24 |
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 New York City (40.71427, -74.00597). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 12,832.9 km |
| Vacuum RTT floor | 85.61 ms |
| Standard fiber RTT floor () | 125.67 ms |
| Low-latency fiber material floor | 125.16 ms |
| Engineering floor (5% path allowance) | 131.97 ms |
| Research 1.33× mapped-fiber reference | 167.14 ms |
| Estimated unamplified path loss | 2694.9 dB |
| Transparent optical spans / inline amplifiers | 169 / 168 |
| Published RTT inflation over fiber floor | 1.76× |
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 | 213.14 ms |
| Average RTT | 221.8 ms |
| Maximum RTT | 261.72 ms |
| Standard deviation | 8.43 ms |
| Stdev / average | 3.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 221.8 ms
- Minimum
- 219.8 ms
- Maximum
- 224.0 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Johannesburg (JNB)
- Destination PoP: New York (NYC)
- Region overview: Africa → North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- New York to Johannesburg latency and RTT — 221.5 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 New York (NYC)
- Ashburn to New York latency and RTT — 6 ms
- Miami to New York latency and RTT — 33.3 ms
- Los Angeles to New York latency and RTT — 57.9 ms
- Seattle to New York latency and RTT — 59.5 ms
- London to New York latency and RTT — 63.8 ms
Same corridor (Africa → North America)
- Johannesburg to Ashburn latency and RTT — 229 ms
- Johannesburg to Miami latency and RTT — 259.9 ms
- Johannesburg to Seattle latency and RTT — 281.2 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-nyc.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → New York 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.