# Singapore → São Paulo, Brazil RTT

🇸🇬 **Singapore (SIN)** → 🇧🇷 **São Paulo, Brazil (GRU)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Singapore to São Paulo, Brazil averaged 311.4 ms, with a minimum of 306.39 ms and a maximum of 332.38 ms across 50 samples. Packet loss was 0%, while the standard deviation was 5.29 ms and jitter was 3.96 ms.

São Paulo is about 15,998 km from Singapore along a great circle, and the fiber-floor estimate for that distance is 156.67 ms. The observed average sits 1.99 times above that floor, translating to a fiber-path efficiency of 50.3%, so the route has considerable headroom compared with a direct-fiber estimate.

This route ranked 18th among the 19 outbound routes in the network's Singapore egress set, making it one of the more demanding paths in this round. Even so, its latency spread is tight relative to the network median variation-to-average figure of 3.28%, meaning the high RTT is consistent rather than erratic.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **311.4 ms**                                                 |
| Jitter               | **3.96 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **156.67 ms**                                                |
| Fiber Efficiency     | **50.3%**                                                    |
| Latency Tier         | High                                                         |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific)   |
| Destination Region   | [South America](/docs/network/latency/regions/south-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 [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) and [São Paulo](https://www.geonames.org/3448439) (-23.54750, -46.63611). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **15,998.2 km** |
| Vacuum RTT floor                              | **106.73 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **156.67 ms**   |
| Low-latency fiber material floor              | **156.04 ms**   |
| Engineering floor (5% path allowance)         | **164.52 ms**   |
| Research 1.33× mapped-fiber reference         | **208.37 ms**   |
| Estimated unamplified path loss               | **3359.6 dB**   |
| Transparent optical spans / inline amplifiers | **210 / 209**   |
| Published RTT inflation over fiber floor      | **1.99×**       |

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        | **306.39 ms** |
| Average RTT        | **311.4 ms**  |
| Maximum RTT        | **332.38 ms** |
| Standard deviation | **5.29 ms**   |
| Stdev / average    | **1.7%**      |

## Route Context

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

* [São Paulo to Singapore latency and RTT](/docs/network/latency/pairs/gru-sin-rtt) — 297.1 ms

**Fastest routes departing Singapore (SIN)**

* [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms
* [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms
* [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 ms

**Fastest routes arriving at São Paulo (GRU)**

* [Ashburn to São Paulo latency and RTT](/docs/network/latency/pairs/iad-gru-rtt) — 101.4 ms
* [New York to São Paulo latency and RTT](/docs/network/latency/pairs/nyc-gru-rtt) — 106.9 ms
* [Miami to São Paulo latency and RTT](/docs/network/latency/pairs/mia-gru-rtt) — 128.7 ms
* [Los Angeles to São Paulo latency and RTT](/docs/network/latency/pairs/lax-gru-rtt) — 131.3 ms
* [Seattle to São Paulo latency and RTT](/docs/network/latency/pairs/sea-gru-rtt) — 155.7 ms

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

* [Tokyo to São Paulo latency and RTT](/docs/network/latency/pairs/tyo-gru-rtt) — 230.5 ms
* [Taipei to São Paulo latency and RTT](/docs/network/latency/pairs/tpe-gru-rtt) — 273 ms
* [Hong Kong to São Paulo latency and RTT](/docs/network/latency/pairs/hkg-gru-rtt) — 287.6 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/sin-gru.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → São Paulo 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/sin-gru-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.