Seattle, USA → São Paulo, Brazil RTT
ICMP round-trip time measurements from Seattle, USA to São Paulo, Brazil: average 155.1 ms, 0% loss, and jitter data. Explore raw latency statistics.
🇺🇸 Seattle, USA (SEA) → 🇧🇷 São Paulo, Brazil (GRU)
Measurement round: 2026-08-15T04:03:13Z.
The 2026-08-15T04:03:13Z ICMP echo RTT test from Seattle to São Paulo averaged 155.1 ms across 50 samples, with a 145.34 ms minimum, 178.16 ms maximum, and zero packet loss.
The 10,902.3 km geodesic distance corresponds to a fiber-floor estimate of about 106.76 ms, so the measured average is 1.45 times that floor, for a fiber efficiency of roughly 68.8%. The 32.8 ms gap between minimum and maximum is reflected in the 6.86 ms jitter figure, though the 7.5 ms standard deviation remains moderate for such a long haul.
This route ranks 15th out of 19 outbound routes from this source by typical latency, and its spread is wider relative to the average than the network-wide median variability of 3.08%. With zero loss and a 'Fair' latency tier, the route is more variable than the best outbound options from this source, and best-case samples sit nearly 10 ms below the average.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 155.1 ms |
| Jitter | 6.86 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 106.76 ms |
| Fiber Efficiency | 68.8% |
| Latency Tier | Fair |
| Source Region | North America |
| Destination Region | 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.
Ping series: SEA → GRU
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 155.1 ± 1.06 ms (SE)
Sample distribution: box = interquartile range (149.5–159.3 ms), median 152.9 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (106.8 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 145.34 |
| 2 | 100 | 154.11 |
| 3 | 200 | 149.09 |
| 4 | 300 | 146.51 |
| 5 | 400 | 169.31 |
| 6 | 500 | 156.84 |
| 7 | 600 | 150.76 |
| 8 | 700 | 147.95 |
| 9 | 800 | 152.03 |
| 10 | 900 | 147.94 |
| 11 | 1000 | 146.25 |
| 12 | 1100 | 145.41 |
| 13 | 1200 | 147.33 |
| 14 | 1300 | 153.24 |
| 15 | 1400 | 158.55 |
| 16 | 1500 | 159.61 |
| 17 | 1600 | 151.68 |
| 18 | 1700 | 171.46 |
| 19 | 1800 | 156.84 |
| 20 | 1900 | 150.06 |
| 21 | 2000 | 160.47 |
| 22 | 2100 | 167.59 |
| 23 | 2200 | 152.94 |
| 24 | 2300 | 152.09 |
| 25 | 2400 | 155.77 |
| 26 | 2500 | 151.40 |
| 27 | 2600 | 148.28 |
| 28 | 2700 | 165.30 |
| 29 | 2800 | 160.33 |
| 30 | 2900 | 167.25 |
| 31 | 3000 | 162.74 |
| 32 | 3100 | 152.91 |
| 33 | 3200 | 153.98 |
| 34 | 3300 | 148.11 |
| 35 | 3400 | 167.80 |
| 36 | 3500 | 154.23 |
| 37 | 3600 | 155.42 |
| 38 | 3700 | 153.05 |
| 39 | 3800 | 149.96 |
| 40 | 3900 | 149.33 |
| 41 | 4000 | 148.88 |
| 42 | 4100 | 149.27 |
| 43 | 4200 | 154.85 |
| 44 | 4300 | 151.24 |
| 45 | 4400 | 178.16 |
| 46 | 4500 | 167.26 |
| 47 | 4600 | 159.70 |
| 48 | 4700 | 150.59 |
| 49 | 4800 | 152.92 |
| 50 | 4900 | 152.87 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Seattle (47.60621, -122.33207) and São Paulo (-23.54750, -46.63611). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 10,902.3 km |
| Vacuum RTT floor | 72.73 ms |
| Standard fiber RTT floor () | 106.76 ms |
| Low-latency fiber material floor | 106.33 ms |
| Engineering floor (5% path allowance) | 112.12 ms |
| Research 1.33× mapped-fiber reference | 142 ms |
| Estimated unamplified path loss | 2289.5 dB |
| Transparent optical spans / inline amplifiers | 144 / 143 |
| Published RTT inflation over fiber floor | 1.45× |
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.
Stability & Trend
The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 145.34 ms |
| Average RTT | 155.1 ms |
| Maximum RTT | 178.16 ms |
| Standard deviation | 7.5 ms |
| Stdev / average | 4.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 155.3 ms
- Minimum
- 154.4 ms
- Maximum
- 156.6 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: São Paulo (GRU)
- Region overview: North America → South America
- Corridor overview: North America to South America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- São Paulo to Seattle latency and RTT — 156 ms
Fastest routes departing Seattle (SEA)
- Seattle to Los Angeles latency and RTT — 26.6 ms
- Seattle to New York latency and RTT — 59 ms
- Seattle to Ashburn latency and RTT — 62 ms
- Seattle to Miami latency and RTT — 81.1 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
Fastest routes arriving at São Paulo (GRU)
- Ashburn to São Paulo latency and RTT — 102.6 ms
- New York to São Paulo latency and RTT — 108.3 ms
- Miami to São Paulo latency and RTT — 129.9 ms
- Los Angeles to São Paulo latency and RTT — 131.1 ms
- London to São Paulo latency and RTT — 171.8 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. Per-pair files are available at /opendata/latency/latest/pairs/sea-gru.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → São Paulo round 2026-08-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.