# Marseille, France → São Paulo, Brazil RTT

🇫🇷 **Marseille, France (MRS)** → 🇧🇷 **São Paulo, Brazil (GRU)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Marseille, France to São Paulo, Brazil averaged 186.7 ms, with a minimum of 176.61 ms and a maximum of 215.07 ms. All 50 probes returned, yielding 0% packet loss; jitter was 6.61 ms and the standard deviation was 7.56 ms.

The average places the route in the Fair latency tier and is 2.09 times the theoretical fiber floor of 89.24 ms, so the measured path is well above the shortest possible fiber route. This path ranks 15th among the 19 outbound routes measured in the round, and its variability relative to the average is about 4%, slightly above the 3.28% median across the 19 outbound paths.

The route-specific takeaway is that the Marseille–São Paulo connection is stable and loss-free, but its distance-adjusted efficiency of 47.8% leaves substantial headroom. Network planners should expect consistent Fair-tier performance rather than a best-case near-optimal path.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **186.7 ms**                                                 |
| Jitter               | **6.61 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **89.24 ms**                                                 |
| Fiber Efficiency     | **47.8%**                                                    |
| 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 [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) 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                      | **9,113 km**  |
| Vacuum RTT floor                              | **60.8 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **89.24 ms**  |
| Low-latency fiber material floor              | **88.88 ms**  |
| Engineering floor (5% path allowance)         | **93.72 ms**  |
| Research 1.33× mapped-fiber reference         | **118.69 ms** |
| Estimated unamplified path loss               | **1913.7 dB** |
| Transparent optical spans / inline amplifiers | **120 / 119** |
| Published RTT inflation over fiber floor      | **2.09×**     |

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        | **176.61 ms** |
| Average RTT        | **186.7 ms**  |
| Maximum RTT        | **215.07 ms** |
| Standard deviation | **7.56 ms**   |
| Stdev / average    | **4.0%**      |

## Route Context

* Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille)
* 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 Marseille latency and RTT](/docs/network/latency/pairs/gru-mrs-rtt) — 187.7 ms

**Fastest routes departing Marseille (MRS)**

* [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms
* [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms
* [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 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/mrs-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → 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/mrs-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.