# São Paulo, Brazil → Hong Kong RTT

🇧🇷 &#x2A;*São Paulo, Brazil (GRU)** → 🇭🇰 &#x2A;*Hong Kong (HKG)**

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

For the 2026-08-16T04:07:28Z round, ICMP echo probes from São Paulo to Hong Kong averaged 273.5 ms, with a minimum of 267.18 ms and a maximum of 286.64 ms. The 50-sample run stayed tight: standard deviation was 4.57 ms, jitter was 4.53 ms, and packet loss was 0%.

The great-circle distance between the two cities is 18,060 km, corresponding to a vacuum one-way floor of 120.48 ms and an approximate fiber floor of 176.86 ms. The observed round-trip time is 1.55 times that fiber floor, or about 64.7% fiber efficiency.

This route ranked 16th of 19 outbound paths measured from São Paulo in this round, placing it in the higher-latency tier. Its standard deviation is about 1.7% of the average, below the 3.28% median stdev-to-average ratio for those 19 paths, so the path is stable despite the high baseline latency.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **273.5 ms**                                                 |
| Jitter               | **4.53 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **176.86 ms**                                                |
| Fiber Efficiency     | **64.7%**                                                    |
| 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 [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469). It does not disclose either facility address.

| Physical Reference                            | Value         |
| --------------------------------------------- | ------------- |
| WGS-84 geodesic distance                      | **18,060 km** |
| Vacuum RTT floor                              | **120.48 ms** |
| Standard fiber RTT floor ($n_g=1.4679$)       | **176.86 ms** |
| Low-latency fiber material floor              | **176.15 ms** |
| Engineering floor (5% path allowance)         | **185.72 ms** |
| Research 1.33× mapped-fiber reference         | **235.22 ms** |
| Estimated unamplified path loss               | **3792.6 dB** |
| Transparent optical spans / inline amplifiers | **238 / 237** |
| Published RTT inflation over fiber floor      | **1.55×**     |

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        | **267.18 ms** |
| Average RTT        | **273.5 ms**  |
| Maximum RTT        | **286.64 ms** |
| Standard deviation | **4.57 ms**   |
| Stdev / average    | **1.7%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* 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**

* [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 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 Hong Kong (HKG)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 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 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

## 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-hkg.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 → Hong Kong 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-hkg-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.
