# Miami, USA → Johannesburg, South Africa RTT

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

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

Miami to Johannesburg averaged 259.8 ms, compared with a 126.78 ms city-centre fiber reference. The difference cannot be assigned to a particular cable or carrier from RTT alone.

Standard deviation was 6.11 ms, or 2.4% of the average. This describes variation within the sample without identifying its cause.

## 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](/docs/network/latency/regions/north-america) |
| Destination Region   | [Africa](/docs/network/latency/regions/africa)               |

## Ping Measurement Series

50 ICMP echo probes were recorded in this round. Individual replies and their distribution are shown below.

## Download This Route's Data

Download the probe round as CSV, JSON or YAML under CC BY 4.0. [Citation details](#about-this-measurement) include the route and round timestamp.

## Theoretical Fiber Latency

The propagation model uses public city-centre coordinates from GeoNames: [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Johannesburg](https://www.geonames.org/993800) (-26.20227, 28.04363). These are not facility coordinates or a surveyed cable path.

| 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×**       |

The span count assumes 80 km optical spans. Attenuation is a power-loss term, not a propagation delay. See the [model assumptions and equations](/docs/network/latency/theoretical-fiber-latency).

## Stability & Trend

Statistics from the same 50 replies. They describe this probe round, not continuous historical monitoring.

| 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%**      |

## Route Context

* Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [Africa](/docs/network/latency/regions/africa)
* 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**

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

**Fastest routes departing Miami (MIA)**

* [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt): 27.3 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt): 33.3 ms
* [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt): 56.8 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt): 81.9 ms
* [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt): 101.8 ms

**Fastest routes arriving at Johannesburg (JNB)**

* [Amsterdam to Johannesburg latency and RTT](/docs/network/latency/pairs/ams-jnb-rtt): 171.9 ms
* [Berlin to Johannesburg latency and RTT](/docs/network/latency/pairs/ber-jnb-rtt): 172.1 ms
* [London to Johannesburg latency and RTT](/docs/network/latency/pairs/lon-jnb-rtt): 179.6 ms
* [Paris to Johannesburg latency and RTT](/docs/network/latency/pairs/par-jnb-rtt): 180.9 ms
* [Frankfurt to Johannesburg latency and RTT](/docs/network/latency/pairs/fra-jnb-rtt): 188.4 ms

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

* [New York to Johannesburg latency and RTT](/docs/network/latency/pairs/nyc-jnb-rtt): 221.5 ms
* [Ashburn to Johannesburg latency and RTT](/docs/network/latency/pairs/iad-jnb-rtt): 228.3 ms
* [Seattle to Johannesburg latency and RTT](/docs/network/latency/pairs/sea-jnb-rtt): 282.1 ms

## About This Measurement

These ICMP measurements cover the two backbone endpoints. Access networks, routing policy and load can change an end user's result. A probe round is not an SLA.

The underlying replies are available under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mia-jnb.pings.{csv,json,yaml}`. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Miami → Johannesburg round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Round published August 16, 2026. See 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/mia-jnb-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.