# Moscow, Russia → São Paulo, Brazil RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇧🇷 **São Paulo, Brazil (GRU)**

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

For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to São Paulo averaged 214.4 ms across 50 samples, with a minimum of 203.61 ms and a maximum of 257.23 ms. The round recorded zero packet loss.

With a great-circle distance near 11,791 km, the fiber floor is about 115.5 ms, so the average represents 1.86 times that floor and a fiber efficiency of 53.9 percent. The path’s 10.55 ms standard deviation and 8.94 ms jitter are modest for the distance, but the 53.6 ms gap between minimum and maximum shows occasional larger swings.

In the Moscow outbound set, this route ranked 17th among 19 paths, while the median variability was 3.28 percent of average latency. São Paulo’s own variability of 10.55 ms is about 4.9 percent of the 214.4 ms average, placing it on the higher-variability side despite stable reachability.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **214.4 ms**                                                 |
| Jitter               | **8.94 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **115.47 ms**                                                |
| Fiber Efficiency     | **53.9%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [Europe](/docs/network/latency/regions/europe)               |
| Destination Region   | [South America](/docs/network/latency/regions/south-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 [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **11,791.1 km** |
| Vacuum RTT floor                              | **78.66 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **115.47 ms**   |
| Low-latency fiber material floor              | **115 ms**      |
| Engineering floor (5% path allowance)         | **121.26 ms**   |
| Research 1.33× mapped-fiber reference         | **153.57 ms**   |
| Estimated unamplified path loss               | **2476.1 dB**   |
| Transparent optical spans / inline amplifiers | **155 / 154**   |
| Published RTT inflation over fiber floor      | **1.86×**       |

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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

| Round Statistic    | Value         |
| ------------------ | ------------- |
| Minimum RTT        | **203.61 ms** |
| Average RTT        | **214.4 ms**  |
| Maximum RTT        | **257.23 ms** |
| Standard deviation | **10.55 ms**  |
| Stdev / average    | **4.9%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [South America](/docs/network/latency/regions/south-america)
* Corridor overview: [Europe to South America](/docs/network/latency/regions/europe-to-south-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**

* [São Paulo to Moscow latency and RTT](/docs/network/latency/pairs/gru-mow-rtt) — 219.5 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 São Paulo (GRU)**

* [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms
* [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms
* [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms
* [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms
* [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms

**Same corridor (Europe → South America)**

* [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 ms
* [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 ms
* [Paris to São Paulo latency and RTT](/docs/network/latency/pairs/par-gru-rtt) — 175.8 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/mow-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → São Paulo round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 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/mow-gru-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.