🇧🇷 São Paulo Ping & Network Latency (GRU) | AS203314
São Paulo (GRU) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇧🇷 São Paulo (GRU)
São Paulo is the internet capital of South America, hosting the region's largest peering ecosystem at PIX. Hats Network's only South American PoP connects the continent to the global backbone.
Measurement round: 2026-08-15T04:03:13Z.
This page provides round-trip time (RTT) latency metrics between the São Paulo (GRU) PoP and every other node on the Hats Network (AS203314) global backbone.
Average RTT from São Paulo to every other PoP
Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round
How to read this chart
Each bar is the average round-trip time of one 50-probe ICMP echo round from São Paulo (GRU) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.
Full 19-destination dataset
| Destination | Avg RTT (ms) | Stdev (ms) | Distance (km) |
|---|---|---|---|
| Johannesburg (JNB) | 332.70 | 13.32 | 7,442 |
| Singapore (SIN) | 295.10 | 12.04 | 15,998 |
| Melbourne (MEL) | 274.70 | 7.74 | 13,105 |
| Hong Kong (HKG) | 273.90 | 13.53 | 18,060 |
| Sydney (SYD) | 266.80 | 8.42 | 13,377 |
| Taipei (TPE) | 259.10 | 6.47 | 18,818 |
| Tokyo (TYO) | 229.60 | 9.16 | 18,530 |
| Moscow (MOW) | 216.20 | 4.68 | 11,791 |
| Berlin (BER) | 190.80 | 6.30 | 10,232 |
| Frankfurt (FRA) | 188.50 | 5.32 | 9,808 |
| Marseille (MRS) | 186.20 | 4.12 | 9,113 |
| Amsterdam (AMS) | 181.30 | 7.54 | 9,782 |
| Paris (PAR) | 179.40 | 8.64 | 9,378 |
| London (LON) | 174.70 | 8.49 | 9,473 |
| Seattle (SEA) | 156.00 | 5.77 | 10,902 |
| Los Angeles (LAX) | 130.80 | 4.78 | 9,895 |
| Ashburn (IAD) | 128.00 | 4.81 | 7,638 |
| New York (NYC) | 122.00 | 1.93 | 7,658 |
| Miami (MIA) | 74.00 | 2.21 | 6,546 |
RTT vs. distance from São Paulo
Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent
How to read this chart
Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from São Paulo. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).
Underlying measurements
| Destination | Avg RTT (ms) | Distance (km) |
|---|---|---|
| Johannesburg (JNB) | 332.70 | 7,442 |
| Singapore (SIN) | 295.10 | 15,998 |
| Melbourne (MEL) | 274.70 | 13,105 |
| Hong Kong (HKG) | 273.90 | 18,060 |
| Sydney (SYD) | 266.80 | 13,377 |
| Taipei (TPE) | 259.10 | 18,818 |
| Tokyo (TYO) | 229.60 | 18,530 |
| Moscow (MOW) | 216.20 | 11,791 |
| Berlin (BER) | 190.80 | 10,232 |
| Frankfurt (FRA) | 188.50 | 9,808 |
| Marseille (MRS) | 186.20 | 9,113 |
| Amsterdam (AMS) | 181.30 | 9,782 |
| Paris (PAR) | 179.40 | 9,378 |
| London (LON) | 174.70 | 9,473 |
| Seattle (SEA) | 156.00 | 10,902 |
| Los Angeles (LAX) | 130.80 | 9,895 |
| Ashburn (IAD) | 128.00 | 7,638 |
| New York (NYC) | 122.00 | 7,658 |
| Miami (MIA) | 74.00 | 6,546 |
Fastest routes into São Paulo
Measured RTT from 19 other PoPs into São Paulo (GRU), sorted fastest first · each row spans min–max with a dot at the average
How to read this chart
Each row is one 50-probe ICMP echo round from another PoP into São Paulo (GRU): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into São Paulo can differ from the outbound path shown in the charts above.
Full 19-source dataset
| Source | Avg RTT (ms) | Min (ms) | Max (ms) | Distance (km) |
|---|---|---|---|---|
| Ashburn (IAD) | 102.60 | 99.89 | 113.70 | 7,638 |
| New York (NYC) | 108.30 | 103.08 | 123.64 | 7,658 |
| Miami (MIA) | 129.90 | 125.41 | 142.80 | 6,546 |
| Los Angeles (LAX) | 131.10 | 126.54 | 143.28 | 9,895 |
| Seattle (SEA) | 155.10 | 145.34 | 178.16 | 10,902 |
| London (LON) | 171.80 | 165.53 | 187.69 | 9,473 |
| Amsterdam (AMS) | 176.50 | 169.40 | 220.99 | 9,782 |
| Paris (PAR) | 176.90 | 172.06 | 197.68 | 9,378 |
| Frankfurt (FRA) | 181.90 | 176.83 | 197.11 | 9,808 |
| Berlin (BER) | 188.00 | 177.96 | 212.46 | 10,232 |
| Marseille (MRS) | 188.10 | 183.87 | 200.39 | 9,113 |
| Moscow (MOW) | 214.90 | 203.74 | 250.81 | 11,791 |
| Tokyo (TYO) | 229.40 | 220.09 | 250.17 | 18,530 |
| Taipei (TPE) | 275.80 | 266.79 | 302.55 | 18,818 |
| Hong Kong (HKG) | 288.80 | 283.45 | 328.46 | 18,060 |
| Sydney (SYD) | 298.00 | 284.09 | 341.12 | 13,377 |
| Melbourne (MEL) | 307.90 | 289.16 | 358.16 | 13,105 |
| Singapore (SIN) | 313.50 | 301.45 | 343.08 | 15,998 |
| Johannesburg (JNB) | 329.80 | 322.61 | 361.85 | 7,442 |
PoP Highlights
- Location: São Paulo, Brazil (South America)
- Region: South America
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 3448439 — -23.54750, -46.63611
- Coverage: RTT measurements to 19 other PoPs across 4 continents
Facility & Interconnection
- Facility: GRU1
- Upstream transit: NTT / Ascenty
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇧🇷 São Paulo (GRU) → 🇺🇸 Miami (MIA) (74 ms) — Excellent |
| Slowest Route | 🇧🇷 São Paulo (GRU) → 🇿🇦 Johannesburg (JNB) (332.7 ms) |
| Average RTT | 203.1 ms |
| Average Jitter | 1.56 ms |
| Average Packet Loss | 0.09% |
| Best Fiber Efficiency | 86.6% |
| Intra-Region Peers | 0 PoP in South America |
| Total Routes | 19 outbound / 19 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
Geographic & Network Position
São Paulo is Hats Network's only PoP in South America. The nearest measured backbone PoP is Miami (MIA) at 74 ms RTT.
São Paulo is South America's internet capital, connecting the continent north to Miami and east across the Atlantic.
Outbound Latency from São Paulo (GRU)
Round-trip time in milliseconds from São Paulo to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇺🇸 Miami (MIA) | 74 | 64.11 ms | 86.6% | 0.49 ms | 0% | Excellent |
| 🇺🇸 New York (NYC) | 122 | 74.99 ms | 61.5% | 0.86 ms | 0.17% | Good |
| 🇺🇸 Ashburn (IAD) | 128 | 74.79 ms | 58.4% | 1.3 ms | 0.08% | Good |
| 🇺🇸 Los Angeles (LAX) | 130.8 | 96.89 ms | 74.1% | 1.19 ms | 0.14% | Good |
| 🇺🇸 Seattle (SEA) | 156 | 106.76 ms | 68.4% | 1.13 ms | 0.16% | Fair |
| 🇬🇧 London (LON) | 174.7 | 92.76 ms | 53.1% | 1.77 ms | 0% | Fair |
| 🇫🇷 Paris (PAR) | 179.4 | 91.83 ms | 51.2% | 1.63 ms | 0.15% | Fair |
| 🇳🇱 Amsterdam (AMS) | 181.3 | 95.79 ms | 52.8% | 1.82 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 186.2 | 89.24 ms | 47.9% | 1.5 ms | 0.18% | Fair |
| 🇩🇪 Frankfurt (FRA) | 188.5 | 96.04 ms | 51% | 1.95 ms | 0.01% | Fair |
| 🇩🇪 Berlin (BER) | 190.8 | 100.2 ms | 52.5% | 0.87 ms | 0.18% | Fair |
| 🇷🇺 Moscow (MOW) | 216.2 | 115.47 ms | 53.4% | 1.52 ms | 0.01% | Fair |
| 🇯🇵 Tokyo (TYO) | 229.6 | 181.46 ms | 79% | 1.41 ms | 0.13% | Fair |
| 🇹🇼 Taipei (TPE) | 259.1 | 184.29 ms | 71.1% | 1.36 ms | 0.14% | High |
| 🇦🇺 Sydney (SYD) | 266.8 | 131 ms | 49.1% | 1.91 ms | 0.07% | High |
| ðŸ‡ðŸ‡° Hong Kong (HKG) | 273.9 | 176.86 ms | 64.6% | 2.21 ms | 0.14% | High |
| 🇦🇺 Melbourne (MEL) | 274.7 | 128.34 ms | 46.7% | 1.98 ms | 0% | High |
| 🇸🇬 Singapore (SIN) | 295.1 | 156.67 ms | 53.1% | 2.91 ms | 0.14% | High |
| 🇿🇦 Johannesburg (JNB) | 332.7 | 72.88 ms | 21.9% | 1.79 ms | 0.09% | High |
Fastest Routes to São Paulo (GRU)
The 10 fastest measured routes to São Paulo, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.
| Rank | Source | Avg RTT | Min | Max | Stdev |
|---|---|---|---|---|---|
| 1 | 🇺🇸 Ashburn (IAD) | 102.6 ms | 99.89 ms | 113.7 ms | 2.91 ms |
| 2 | 🇺🇸 New York (NYC) | 108.3 ms | 103.08 ms | 123.64 ms | 4.41 ms |
| 3 | 🇺🇸 Miami (MIA) | 129.9 ms | 125.41 ms | 142.8 ms | 4.21 ms |
| 4 | 🇺🇸 Los Angeles (LAX) | 131.1 ms | 126.54 ms | 143.28 ms | 3.5 ms |
| 5 | 🇺🇸 Seattle (SEA) | 155.1 ms | 145.34 ms | 178.16 ms | 7.5 ms |
| 6 | 🇬🇧 London (LON) | 171.8 ms | 165.53 ms | 187.69 ms | 5.45 ms |
| 7 | 🇳🇱 Amsterdam (AMS) | 176.5 ms | 169.4 ms | 220.99 ms | 8.59 ms |
| 8 | 🇫🇷 Paris (PAR) | 176.9 ms | 172.06 ms | 197.68 ms | 5.39 ms |
| 9 | 🇩🇪 Frankfurt (FRA) | 181.9 ms | 176.83 ms | 197.11 ms | 4.39 ms |
| 10 | 🇩🇪 Berlin (BER) | 188 ms | 177.96 ms | 212.46 ms | 8.06 ms |
Inbound Latency to São Paulo (GRU)
Round-trip time in milliseconds from all other PoPs to São Paulo. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇺🇸 Ashburn (IAD) | 102.6 | 74.79 ms | 72.9% | 0.83 ms | 0.15% | Good |
| 🇺🇸 New York (NYC) | 108.3 | 74.99 ms | 69.2% | 1.13 ms | 0.13% | Good |
| 🇺🇸 Miami (MIA) | 129.9 | 64.11 ms | 49.4% | 1.36 ms | 0.07% | Good |
| 🇺🇸 Los Angeles (LAX) | 131.1 | 96.89 ms | 73.9% | 0.64 ms | 0% | Good |
| 🇺🇸 Seattle (SEA) | 155.1 | 106.76 ms | 68.8% | 1.4 ms | 0% | Fair |
| 🇬🇧 London (LON) | 171.8 | 92.76 ms | 54% | 1.99 ms | 0% | Fair |
| 🇳🇱 Amsterdam (AMS) | 176.5 | 95.79 ms | 54.3% | 1.62 ms | 0.17% | Fair |
| 🇫🇷 Paris (PAR) | 176.9 | 91.83 ms | 51.9% | 1.2 ms | 0% | Fair |
| 🇩🇪 Frankfurt (FRA) | 181.9 | 96.04 ms | 52.8% | 1.81 ms | 0.17% | Fair |
| 🇩🇪 Berlin (BER) | 188 | 100.2 ms | 53.3% | 2.19 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 188.1 | 89.24 ms | 47.4% | 2.22 ms | 0.01% | Fair |
| 🇷🇺 Moscow (MOW) | 214.9 | 115.47 ms | 53.7% | 2.56 ms | 0% | Fair |
| 🇯🇵 Tokyo (TYO) | 229.4 | 181.46 ms | 79.1% | 1.97 ms | 0% | Fair |
| 🇹🇼 Taipei (TPE) | 275.8 | 184.29 ms | 66.8% | 1.86 ms | 0.06% | High |
| ðŸ‡ðŸ‡° Hong Kong (HKG) | 288.8 | 176.86 ms | 61.2% | 1.35 ms | 0% | High |
| 🇦🇺 Sydney (SYD) | 298 | 131 ms | 44% | 2.86 ms | 0% | High |
| 🇦🇺 Melbourne (MEL) | 307.9 | 128.34 ms | 41.7% | 1.79 ms | 0% | High |
| 🇸🇬 Singapore (SIN) | 313.5 | 156.67 ms | 50% | 2.3 ms | 0% | High |
| 🇿🇦 Johannesburg (JNB) | 329.8 | 72.88 ms | 22.1% | 1.73 ms | 0.16% | High |
Frequently Asked Questions
What is the fastest route to São Paulo?
The fastest measured route to São Paulo (GRU) is Ashburn (IAD) → São Paulo (GRU), averaging 102.6 ms RTT (Good).
What is the fastest route from São Paulo?
The fastest measured route from São Paulo (GRU) is São Paulo (GRU) → Miami (MIA), averaging 74 ms RTT (Excellent).
How well connected is São Paulo to the Hats Network backbone?
São Paulo (GRU) maintains measured routes to all 19 other PoPs across 4 continents. The slowest route, São Paulo (GRU) → Johannesburg (JNB), averages 332.7 ms RTT.
Open Data
Measured latency data for São Paulo (GRU) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:
- Per-route files — every directed route from São Paulo is published as
gru-<destination>.pings.{csv,json,yaml}under/opendata/latency/latest/pairs/— for example gru-mia.pings.csv, the 50-probe ICMP echo round for São Paulo (GRU) → Miami (MIA). - Dataset documentation — /opendata/latency/ covers file formats, versioning, checksums, and the aggregated full-matrix releases.
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.
🇺🇸 Seattle Ping & Network Latency (SEA) | AS203314
Seattle (SEA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
ðŸ‡ðŸ‡° Hong Kong Ping & Network Latency (HKG) | AS203314
Hong Kong (HKG) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.