# São Paulo, Brazil → Taipei, Taiwan RTT

🇧🇷 **São Paulo, Brazil (GRU)** → 🇹🇼 **Taipei, Taiwan (TPE)**

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

In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo requests from São Paulo, Brazil to Taipei, Taiwan produced an average round-trip time of 259.1 ms, with a minimum of 248.08 ms and a maximum of 296.38 ms. The standard deviation was 8.63 ms, jitter was 7.16 ms, and packet loss was zero.

The geodesic distance is 18,818.5 km, and the fiber floor is 184.29 ms, so the observed average sits at 1.41 times that floor. This gives a route efficiency of 71.1 percent, a relatively strong result for such a long intercontinental path.

Within the 19 outbound routes measured from São Paulo, Taipei ranked 14th, placing it in the slower half of the group. The broader set's median variability was 3.28 percent of average latency; this route's 8.63 ms standard deviation is about 3.3 percent of its 259.1 ms average, aligning closely with the typical range.

The minimum RTT of 248.08 ms is much closer to the average than the maximum, so occasional slower probes widen the range more than steady variation. Still, with zero loss and jitter under 8 ms, the high-latency tier here reflects distance and route efficiency rather than packet instability.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **259.1 ms**                                                 |
| Jitter               | **7.16 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **184.29 ms**                                                |
| Fiber Efficiency     | **71.1%**                                                    |
| Latency Tier         | High                                                         |
| 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 [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **18,818.5 km** |
| Vacuum RTT floor                              | **125.54 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **184.29 ms**   |
| Low-latency fiber material floor              | **183.54 ms**   |
| Engineering floor (5% path allowance)         | **193.52 ms**   |
| Research 1.33× mapped-fiber reference         | **245.1 ms**    |
| Estimated unamplified path loss               | **3951.9 dB**   |
| Transparent optical spans / inline amplifiers | **247 / 246**   |
| Published RTT inflation over fiber floor      | **1.41×**       |

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        | **248.08 ms** |
| Average RTT        | **259.1 ms**  |
| Maximum RTT        | **296.38 ms** |
| Standard deviation | **8.63 ms**   |
| Stdev / average    | **3.3%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* 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**

* [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 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 Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms

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

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