# São Paulo, Brazil → Sydney, Australia RTT

🇧🇷 **São Paulo, Brazil (GRU)** → 🇦🇺 **Sydney, Australia (SYD)**

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

For the 2026-08-16T04:07:28Z round, 50 ICMP echo requests from São Paulo, Brazil to Sydney, Australia returned an average round-trip time of 265.5 ms, with a minimum of 255.6 ms and a maximum of 295.52 ms. The standard deviation of 9.22 ms and jitter of 8.27 ms indicate a fairly steady path, and no packets were lost.

At 13,377 km apart, even a realistic fiber path has a floor near 131 ms, so the observed 265.5 ms average sits at 2.03 times that floor. This works out to 49.3 percent efficiency relative to the physical reference, meaning the route uses roughly half of its best-case optical headroom.

Against the 19 outbound routes from São Paulo measured in the same round, Sydney ranked 15th, placing it in the slower half of the set. Across those 19 routes, the median spread of latency variability was 3.28 percent of average RTT; the 9.22 ms standard deviation here represents about 3.5 percent of the 265.5 ms average, tracking close to that typical dispersion.

The route's standout feature is its inflation factor rather than instability: zero packet loss and moderate jitter accompany an average latency more than double the fiber floor, a useful distinction for anyone evaluating long-haul network paths from Brazil to Australia.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **265.5 ms**                                                 |
| Jitter               | **8.27 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **131 ms**                                                   |
| Fiber Efficiency     | **49.3%**                                                    |
| 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 [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732). It does not disclose either facility address.

| Physical Reference                            | Value         |
| --------------------------------------------- | ------------- |
| WGS-84 geodesic distance                      | **13,377 km** |
| Vacuum RTT floor                              | **89.24 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **131 ms**    |
| Low-latency fiber material floor              | **130.47 ms** |
| Engineering floor (5% path allowance)         | **137.57 ms** |
| Research 1.33× mapped-fiber reference         | **174.23 ms** |
| Estimated unamplified path loss               | **2809.2 dB** |
| Transparent optical spans / inline amplifiers | **176 / 175** |
| Published RTT inflation over fiber floor      | **2.03×**     |

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        | **255.6 ms**  |
| Average RTT        | **265.5 ms**  |
| Maximum RTT        | **295.52 ms** |
| Standard deviation | **9.22 ms**   |
| Stdev / average    | **3.5%**      |

## Route Context

* Departure PoP: [São Paulo (GRU)](/docs/network/latency/gru-sao-paulo)
* Destination PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney)
* 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**

* [Sydney to São Paulo latency and RTT](/docs/network/latency/pairs/syd-gru-rtt) — 296.7 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 Sydney (SYD)**

* [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms
* [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms
* [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms
* [Taipei to Sydney latency and RTT](/docs/network/latency/pairs/tpe-syd-rtt) — 133.2 ms
* [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 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 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-syd.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 → Sydney 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-syd-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.