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

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

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests between São Paulo, Brazil and Miami, USA averaged 74ms over 50 samples, with a minimum of 70.55ms and a maximum of 83.79ms. The 3.07ms standard deviation and 2.29ms jitter show a stable profile, and packet loss was zero.

That 74ms average is only about 15% above the theoretical fiber floor of 64.11ms for the 6,546.4km great-circle distance, yielding an 86.6% fiber efficiency. The route is running close to the propagation limit for light in fiber, leaving little room for latency improvement on this geography.

This path ranks first among the 19 outbound routes in the round, while its variability ratio of about 4.1% sits slightly above the network median of 3.28%. With an Excellent latency tier, no loss, and very low jitter, this is a strong reference for São Paulo-to-Miami connectivity.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **74 ms**                                                    |
| Jitter               | **2.29 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **64.11 ms**                                                 |
| Fiber Efficiency     | **86.6%**                                                    |
| Latency Tier         | Excellent                                                    |
| Source Region        | [South America](/docs/network/latency/regions/south-america) |
| Destination Region   | [North America](/docs/network/latency/regions/north-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 [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **6,546.4 km** |
| Vacuum RTT floor                              | **43.67 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **64.11 ms**   |
| Low-latency fiber material floor              | **63.85 ms**   |
| Engineering floor (5% path allowance)         | **67.32 ms**   |
| Research 1.33× mapped-fiber reference         | **85.26 ms**   |
| Estimated unamplified path loss               | **1374.7 dB**  |
| Transparent optical spans / inline amplifiers | **86 / 85**    |
| Published RTT inflation over fiber floor      | **1.15×**      |

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        | **70.55 ms** |
| Average RTT        | **74 ms**    |
| Maximum RTT        | **83.79 ms** |
| Standard deviation | **3.07 ms**  |
| Stdev / average    | **4.1%**     |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Region overview: [South America](/docs/network/latency/regions/south-america) → [North America](/docs/network/latency/regions/north-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**

* [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms

**Fastest routes departing São Paulo (GRU)**

* [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
* [São Paulo to London latency and RTT](/docs/network/latency/pairs/gru-lon-rtt) — 175.8 ms

**Fastest routes arriving at Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms
* [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 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-mia.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 → Miami 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-mia-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.