# Moscow, Russia → Johannesburg, South Africa RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇿🇦 **Johannesburg, South Africa (JNB)**

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

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

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

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **201.9 ms**                                   |
| Jitter               | **7.49 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **89.37 ms**                                   |
| Fiber Efficiency     | **44.3%**                                      |
| Latency Tier         | Fair                                           |
| Source Region        | [Europe](/docs/network/latency/regions/europe) |
| 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: [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) 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                      | **9,125.7 km** |
| Vacuum RTT floor                              | **60.88 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **89.37 ms**   |
| Low-latency fiber material floor              | **89.01 ms**   |
| Engineering floor (5% path allowance)         | **93.85 ms**   |
| Research 1.33× mapped-fiber reference         | **118.86 ms**  |
| Estimated unamplified path loss               | **1916.4 dB**  |
| Transparent optical spans / inline amplifiers | **120 / 119**  |
| Published RTT inflation over fiber floor      | **2.26×**      |

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        | **192.01 ms** |
| Average RTT        | **201.9 ms**  |
| Maximum RTT        | **232.17 ms** |
| Standard deviation | **7.94 ms**   |
| Stdev / average    | **3.9%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Johannesburg (JNB)](/docs/network/latency/jnb-johannesburg)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [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 Moscow latency and RTT](/docs/network/latency/pairs/jnb-mow-rtt): 200.7 ms

**Fastest routes departing Moscow (MOW)**

* [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt): 27.5 ms
* [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt): 35.9 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt): 37.6 ms
* [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt): 42.4 ms
* [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt): 44 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 (Europe → Africa)**

* [Marseille to Johannesburg latency and RTT](/docs/network/latency/pairs/mrs-jnb-rtt): 198.5 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/mow-jnb.pings.{csv,json,yaml}`. Cite the route, round timestamp and dataset version. Example: "Hats Network latency dataset, Moscow → 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/mow-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.