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

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

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

In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo to Moscow produced an average RTT of 219.5 ms, with a minimum of 208.05 ms and a maximum of 246.05 ms. The path had zero packet loss, a 7.63 ms standard deviation, and 6.64 ms jitter.

For the 11,791.1 km great-circle distance, the fiber floor is 115.47 ms; the observed average is 1.9 times that floor, giving a 52.6% fiber efficiency and a “Fair” latency tier. The 38 ms gap between the fastest and slowest probes indicates moderate variability over the long crossing.

This route ranks 12th among the 19 outbound São Paulo routes, with the median variability for those 19 paths at 3.28% of average RTT. Moscow’s standard deviation equals about 3.5% of its average, so stability is close to the median but slightly looser, and the zero-loss result stands out for such a long haul.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **219.5 ms**                                                 |
| Jitter               | **6.64 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **115.47 ms**                                                |
| Fiber Efficiency     | **52.6%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [South America](/docs/network/latency/regions/south-america) |
| Destination Region   | [Europe](/docs/network/latency/regions/europe)               |

## 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 [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). 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.9×**        |

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        | **208.05 ms** |
| Average RTT        | **219.5 ms**  |
| Maximum RTT        | **246.05 ms** |
| Standard deviation | **7.63 ms**   |
| Stdev / average    | **3.5%**      |

## Route Context

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

* [Moscow to São Paulo latency and RTT](/docs/network/latency/pairs/mow-gru-rtt) — 214.4 ms

**Fastest routes departing São Paulo (GRU)**

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

**Fastest routes arriving at Moscow (MOW)**

* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms
* [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms
* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms

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

* [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms
* [São Paulo to Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms
* [São Paulo to Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/gru-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, São Paulo → Moscow 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/gru-mow-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.