# Frankfurt, Germany → São Paulo, Brazil RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇧🇷 **São Paulo, Brazil (GRU)**

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

During the 2026-08-16T04:07:28Z round, ICMP echo requests from Frankfurt to São Paulo averaged 181.3 ms over 50 samples, with a minimum of 176.28 ms, a maximum of 197.75 ms and zero packet loss. A 3.73 ms standard deviation and 3.34 ms jitter keep the route's variability at about 2.1% of the average, tighter than the 3.28% median for the 19-route set.

Ranked 15th of 19 outbound routes by average RTT, this path is among the slower half of the set, consistent with a great-circle distance of 9,807.7 km. Its average is 1.89 times the theoretical fiber floor of 96.04 ms, giving a fiber efficiency of 53%.

The notable feature is consistency: 50 consecutive probes with no loss and a standard deviation below 4 ms mean the high latency is steady rather than erratic. The Fair latency tier reflects the high absolute RTT, not instability, making the 181.3 ms average a stable reference point for this long-haul route.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **181.3 ms**                                                 |
| Jitter               | **3.34 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **96.04 ms**                                                 |
| Fiber Efficiency     | **53%**                                                      |
| 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 [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) 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,807.7 km** |
| Vacuum RTT floor                              | **65.43 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **96.04 ms**   |
| Low-latency fiber material floor              | **95.66 ms**   |
| Engineering floor (5% path allowance)         | **100.86 ms**  |
| Research 1.33× mapped-fiber reference         | **127.74 ms**  |
| Estimated unamplified path loss               | **2059.6 dB**  |
| Transparent optical spans / inline amplifiers | **129 / 128**  |
| Published RTT inflation over fiber floor      | **1.89×**      |

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.28 ms** |
| Average RTT        | **181.3 ms**  |
| Maximum RTT        | **197.75 ms** |
| Standard deviation | **3.73 ms**   |
| Stdev / average    | **2.1%**      |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* 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 Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.2 ms

**Fastest routes departing Frankfurt (FRA)**

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