# São Paulo, Brazil → Amsterdam, Netherlands RTT

🇧🇷 **São Paulo, Brazil (GRU)** → 🇳🇱 **Amsterdam, Netherlands (AMS)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to Amsterdam, Netherlands averaged 180 ms across 50 samples, with a minimum of 172.52 ms, a maximum of 196.27 ms, and no packet loss.

Average RTT places the route in the Fair latency tier, while the 6.11 ms standard deviation and 5.36 ms jitter define its consistency. It ranks 7th among the 19 outbound routes from São Paulo in this measurement round.

The average sits 1.88 times above the fiber-floor estimate of 95.79 ms, giving a 53.2% fiber-efficiency figure. Relative to the median variability of 3.28% for the outbound route set, the route's 3.39% stdev-to-average ratio is closely in line, so the delay is dominated by the transatlantic distance rather than by packet loss.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **180 ms**                                                   |
| Jitter               | **5.36 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **95.79 ms**                                                 |
| Fiber Efficiency     | **53.2%**                                                    |
| 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 [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,781.6 km** |
| Vacuum RTT floor                              | **65.26 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **95.79 ms**   |
| Low-latency fiber material floor              | **95.4 ms**    |
| Engineering floor (5% path allowance)         | **100.59 ms**  |
| Research 1.33× mapped-fiber reference         | **127.4 ms**   |
| Estimated unamplified path loss               | **2054.1 dB**  |
| Transparent optical spans / inline amplifiers | **129 / 128**  |
| Published RTT inflation over fiber floor      | **1.88×**      |

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        | **172.52 ms** |
| Average RTT        | **180 ms**    |
| Maximum RTT        | **196.27 ms** |
| Standard deviation | **6.11 ms**   |
| Stdev / average    | **3.4%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* 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**

* [Amsterdam to São Paulo latency and RTT](/docs/network/latency/pairs/ams-gru-rtt) — 175.5 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 Amsterdam (AMS)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms
* [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 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 Paris latency and RTT](/docs/network/latency/pairs/gru-par-rtt) — 180.2 ms
* [São Paulo to Frankfurt latency and RTT](/docs/network/latency/pairs/gru-fra-rtt) — 186.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-ams.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 → Amsterdam 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-ams-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.