# Johannesburg to Miami Latency, Ping & RTT | AS203314

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

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

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

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

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **259.3 ms**                                                 |
| Jitter               | **3.54 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **126.78 ms**                                                |
| Fiber Efficiency     | **48.9%**                                                    |
| Latency Tier         | High                                                         |
| Source Region        | [Africa](/docs/network/latency/regions/africa)               |
| Destination Region   | [North America](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). 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](/docs/network/latency/theoretical-fiber-latency).

## 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        | **254.52 ms** |
| Average RTT        | **259.3 ms**  |
| Maximum RTT        | **274.01 ms** |
| Standard deviation | **4.41 ms**   |
| Stdev / average    | **1.7%**      |

## Route Context

* Departure PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Region overview: [Africa](/docs/network/latency/regions/africa) → [North America](/docs/network/latency/regions/north-america)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Miami to Johannesburg latency and RTT](/docs/network/latency/pairs/mia-jnb-rtt) — 259.4 ms

**Fastest routes departing Johannesburg (JNB)**

* [Johannesburg to London latency and RTT](/docs/network/latency/pairs/jnb-lon-rtt) — 158 ms
* [Johannesburg to Amsterdam latency and RTT](/docs/network/latency/pairs/jnb-ams-rtt) — 163.2 ms
* [Johannesburg to Paris latency and RTT](/docs/network/latency/pairs/jnb-par-rtt) — 164.4 ms
* [Johannesburg to Frankfurt latency and RTT](/docs/network/latency/pairs/jnb-fra-rtt) — 166 ms
* [Johannesburg to Marseille latency and RTT](/docs/network/latency/pairs/jnb-mrs-rtt) — 172 ms

**Fastest routes arriving at Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 28.3 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 34.1 ms
* [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 85.3 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 88.1 ms

**Same corridor (Africa → North America)**

* [Johannesburg to New York latency and RTT](/docs/network/latency/pairs/jnb-nyc-rtt) — 221.6 ms
* [Johannesburg to Ashburn latency and RTT](/docs/network/latency/pairs/jnb-iad-rtt) — 228.5 ms
* [Johannesburg to Seattle latency and RTT](/docs/network/latency/pairs/jnb-sea-rtt) — 280.3 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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/jnb-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round date, and the dataset version — for example: "Hats Network latency dataset, Johannesburg → Miami round 2026-08-10, CC BY 4.0".

***

*Data auto-generated on August 10, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/jnb-mia-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.