# Seattle, USA → São Paulo, Brazil RTT

🇺🇸 **Seattle, USA (SEA)** → 🇧🇷 **São Paulo, Brazil (GRU)**

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

In the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Seattle to São Paulo returned an average round-trip time of 155.7 ms, with a minimum of 152.75 ms and a maximum of 163 ms. There was no packet loss, and jitter of 2.3 ms is modest for an intercontinental distance of 10,902.3 km, though the average places the route in the Fair latency tier.

Against a vacuum floor of 72.73 ms and a fiber floor of 106.76 ms, the observed average is 1.46 times the fiber floor, or a fiber efficiency of 68.6%. That puts the measured mean 48.94 ms above the fiber-floor estimate for the geodesic distance.

Among the 19 outbound routes measured from Seattle in this round, this path ranks 15th, so most alternatives reached São Paulo with lower latency. Its stability is better than the route-family median: the 2.37 ms standard deviation is only about 1.5% of the average versus a 3.28% median, making the latency dependable even if not the quickest.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **155.7 ms**                                                 |
| Jitter               | **2.3 ms**                                                   |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **106.76 ms**                                                |
| Fiber Efficiency     | **68.6%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| 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 [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) 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                      | **10,902.3 km** |
| Vacuum RTT floor                              | **72.73 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **106.76 ms**   |
| Low-latency fiber material floor              | **106.33 ms**   |
| Engineering floor (5% path allowance)         | **112.12 ms**   |
| Research 1.33× mapped-fiber reference         | **142 ms**      |
| Estimated unamplified path loss               | **2289.5 dB**   |
| Transparent optical spans / inline amplifiers | **144 / 143**   |
| Published RTT inflation over fiber floor      | **1.46×**       |

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        | **152.75 ms** |
| Average RTT        | **155.7 ms**  |
| Maximum RTT        | **163 ms**    |
| Standard deviation | **2.37 ms**   |
| Stdev / average    | **1.5%**      |

## Route Context

* Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* Destination PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [South America](/docs/network/latency/regions/south-america)
* Corridor overview: [North America to South America](/docs/network/latency/regions/north-america-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 Seattle latency and RTT](/docs/network/latency/pairs/gru-sea-rtt) — 155.9 ms

**Fastest routes departing Seattle (SEA)**

* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 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
* [London to São Paulo latency and RTT](/docs/network/latency/pairs/lon-gru-rtt) — 170.7 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/sea-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → 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/sea-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.