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

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

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

At round 2026-08-16T04:07:28Z, ICMP echo requests from Amsterdam, Netherlands to São Paulo, Brazil spent an average of 175.5 ms in round-trip transit across 50 samples, with a minimum of 166.82 ms and a maximum of 195.11 ms.

There was no packet loss, but the route's standard deviation was 6.86 ms and jitter was 6.92 ms, so the largest observed round-trip time exceeded the smallest by more than 28 ms. Within the 19 outbound routes from Amsterdam measured in this round, this route ranked 16th by average latency, placing it near the slower end of the set; its standard deviation is about 3.9% of its average, close to but above the median route's 3.28% ratio.

The physical reference is a geodesic distance of 9,781.6 km, with a vacuum floor of 65.26 ms and a fiber floor of 95.79 ms. The measured average sits at 1.83 times the fiber floor, equivalent to 54.6% fiber efficiency, indicating that the path carries substantial additional round-trip time beyond the ideal fiber estimate.

With zero loss but jitter near 7 ms, the route remained available throughout the sample window while individual round-trip values varied noticeably; treat the 166.82–195.11 ms range as this route's observed envelope.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **175.5 ms**                                                 |
| Jitter               | **6.92 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **95.79 ms**                                                 |
| Fiber Efficiency     | **54.6%**                                                    |
| 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 [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) 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,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.83×**      |

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        | **166.82 ms** |
| Average RTT        | **175.5 ms**  |
| Maximum RTT        | **195.11 ms** |
| Standard deviation | **6.86 ms**   |
| Stdev / average    | **3.9%**      |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* 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 Amsterdam latency and RTT](/docs/network/latency/pairs/gru-ams-rtt) — 180 ms

**Fastest routes departing Amsterdam (AMS)**

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