# São Paulo, Brazil → Tokyo, Japan RTT

🇧🇷 **São Paulo, Brazil (GRU)** → 🇯🇵 **Tokyo, Japan (TYO)**

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

In the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo, Brazil to Tokyo, Japan produced an average round-trip time of 230.3 ms, with a minimum of 223.73 ms and a maximum of 259.55 ms. Standard deviation was 6.53 ms, jitter was 4.44 ms, and packet loss was zero.

At 18,530.2 km, the fiber floor is 181.46 ms, and the observed average is only 1.27 times that floor, for a route efficiency of 78.8 percent. The low jitter and zero loss make this a comparatively well-behaved long-distance path.

Tokyo ranked 13th among the 19 outbound routes from São Paulo, placing it slightly in the slower half of the set. The median variability across those routes was 3.28 percent of average latency; this route's 6.53 ms standard deviation equals about 2.8 percent of its 230.3 ms average, a bit tighter than the typical spread.

The most useful signal here is the combination of efficiency and stability: the route stays close to its physical reference while maintaining a narrow jitter range, suggesting the fair latency tier reflects the long distance more than inconsistent network behavior.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **230.3 ms**                                                 |
| Jitter               | **4.44 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **181.46 ms**                                                |
| Fiber Efficiency     | **78.8%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [South America](/docs/network/latency/regions/south-america) |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/asia-pacific)   |

## 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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **18,530.2 km** |
| Vacuum RTT floor                              | **123.62 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **181.46 ms**   |
| Low-latency fiber material floor              | **180.73 ms**   |
| Engineering floor (5% path allowance)         | **190.56 ms**   |
| Research 1.33× mapped-fiber reference         | **241.34 ms**   |
| Estimated unamplified path loss               | **3891.3 dB**   |
| Transparent optical spans / inline amplifiers | **244 / 243**   |
| Published RTT inflation over fiber floor      | **1.27×**       |

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        | **223.73 ms** |
| Average RTT        | **230.3 ms**  |
| Maximum RTT        | **259.55 ms** |
| Standard deviation | **6.53 ms**   |
| Stdev / average    | **2.8%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* Region overview: [South America](/docs/network/latency/regions/south-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* 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**

* [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.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 Tokyo (TYO)**

* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms
* [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms

**Same corridor (South America → Asia Pacific)**

* [São Paulo to Taipei latency and RTT](/docs/network/latency/pairs/gru-tpe-rtt) — 259.1 ms
* [São Paulo to Sydney latency and RTT](/docs/network/latency/pairs/gru-syd-rtt) — 265.5 ms
* [São Paulo to Hong Kong latency and RTT](/docs/network/latency/pairs/gru-hkg-rtt) — 273.5 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-tyo.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 → Tokyo 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-tyo-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.