# São Paulo, Brazil → New York, USA RTT

🇧🇷 **São Paulo, Brazil (GRU)** → 🇺🇸 **New York, USA (NYC)**

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

For the 2026-08-16T04:07:28Z round, ICMP echo RTT from São Paulo, Brazil to New York, USA averaged 122ms across 50 samples, ranging from 116.85ms to 132.54ms. The 3.8ms standard deviation and 3.62ms jitter are modest, and all probes were returned without loss.

The average sits 63% above the theoretical fiber floor of 74.99ms for the 7,657.6km great-circle distance, translating to a 61.5% fiber efficiency. This is a larger overhead than a near-optimal path would show, though the round-trip times remain consistent.

This path is ranked second among the 19 outbound routes in the round, and its variability ratio of about 3.1% falls below the network median of 3.28%. The zero-loss result and contained jitter make it a dependable reference for São Paulo-to-New York latency, with the extra distance overhead being the main separating factor from a tighter fiber-floor result.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **122 ms**                                                   |
| Jitter               | **3.62 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **74.99 ms**                                                 |
| Fiber Efficiency     | **61.5%**                                                    |
| Latency Tier         | Good                                                         |
| 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **7,657.6 km** |
| Vacuum RTT floor                              | **51.09 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **74.99 ms**   |
| Low-latency fiber material floor              | **74.69 ms**   |
| Engineering floor (5% path allowance)         | **78.75 ms**   |
| Research 1.33× mapped-fiber reference         | **99.74 ms**   |
| Estimated unamplified path loss               | **1608.1 dB**  |
| Transparent optical spans / inline amplifiers | **101 / 100**  |
| Published RTT inflation over fiber floor      | **1.63×**      |

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        | **116.85 ms** |
| Average RTT        | **122 ms**    |
| Maximum RTT        | **132.54 ms** |
| Standard deviation | **3.8 ms**    |
| Stdev / average    | **3.1%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* 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**

* [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 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 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 New York (NYC)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.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/gru-nyc.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 → New York 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-nyc-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.