🇧🇷 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 18 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.
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.
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 18 other PoPs across 3 continents
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇧🇷 São Paulo (GRU) → 🇺🇸 Miami (MIA) (74 ms) — Excellent |
| Slowest Route | 🇧🇷 São Paulo (GRU) → 🇸🇬 Singapore (SIN) (297.1 ms) |
| Average RTT | 197.5 ms |
| Average Jitter | 1.58 ms |
| Average Packet Loss | 0.07% |
| Best Fiber Efficiency | 86.6% |
| Intra-Region Peers | 0 PoP in South America |
| Total Routes | 18 outbound / 18 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
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.68 ms | 0% | Excellent |
| 🇺🇸 New York (NYC) | 122 | 74.99 ms | 61.5% | 1.11 ms | 0% | Good |
| 🇺🇸 Ashburn (IAD) | 128 | 74.79 ms | 58.4% | 0.83 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 131.6 | 96.89 ms | 73.6% | 0.82 ms | 0.11% | Good |
| 🇺🇸 Seattle (SEA) | 156.1 | 106.76 ms | 68.4% | 1.63 ms | 0.14% | Fair |
| 🇬🇧 London (LON) | 175.7 | 92.76 ms | 52.8% | 1.71 ms | 0.06% | Fair |
| 🇫🇷 Paris (PAR) | 181.6 | 91.83 ms | 50.6% | 1.24 ms | 0.08% | Fair |
| 🇳🇱 Amsterdam (AMS) | 182 | 95.79 ms | 52.6% | 1.02 ms | 0.05% | Fair |
| 🇩🇪 Frankfurt (FRA) | 188.1 | 96.04 ms | 51.1% | 2.2 ms | 0.04% | Fair |
| 🇩🇪 Berlin (BER) | 193.4 | 100.2 ms | 51.8% | 0.99 ms | 0.14% | Fair |
| 🇫🇷 Marseille (MRS) | 194.8 | 89.24 ms | 45.8% | 1.99 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 218.1 | 115.47 ms | 52.9% | 1.15 ms | 0.15% | Fair |
| 🇯🇵 Tokyo (TYO) | 231.9 | 181.46 ms | 78.3% | 1.64 ms | 0.14% | Fair |
| 🇹🇼 Taipei (TPE) | 261.9 | 184.29 ms | 70.4% | 1.94 ms | 0.16% | High |
| 🇦🇺 Sydney (SYD) | 267.2 | 131 ms | 49% | 2.42 ms | 0% | High |
| ðŸ‡ðŸ‡° Hong Kong (HKG) | 275.2 | 176.86 ms | 64.3% | 1.87 ms | 0% | High |
| 🇦🇺 Melbourne (MEL) | 276.6 | 128.34 ms | 46.4% | 2.14 ms | 0.11% | High |
| 🇸🇬 Singapore (SIN) | 297.1 | 156.67 ms | 52.7% | 3.03 ms | 0.04% | High |
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) | 107.5 | 74.79 ms | 69.6% | 0.89 ms | 0% | Good |
| 🇺🇸 New York (NYC) | 113.4 | 74.99 ms | 66.1% | 1.05 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 131.1 | 96.89 ms | 73.9% | 1.32 ms | 0.18% | Good |
| 🇺🇸 Miami (MIA) | 141.2 | 64.11 ms | 45.4% | 1.38 ms | 0.05% | Good |
| 🇺🇸 Seattle (SEA) | 155.1 | 106.76 ms | 68.8% | 1.24 ms | 0.07% | Fair |
| 🇬🇧 London (LON) | 177.6 | 92.76 ms | 52.2% | 1.58 ms | 0.07% | Fair |
| 🇫🇷 Paris (PAR) | 181.7 | 91.83 ms | 50.5% | 1.59 ms | 0.17% | Fair |
| 🇳🇱 Amsterdam (AMS) | 182.4 | 95.79 ms | 52.5% | 1.21 ms | 0% | Fair |
| 🇩🇪 Frankfurt (FRA) | 187.7 | 96.04 ms | 51.2% | 0.94 ms | 0.05% | Fair |
| 🇩🇪 Berlin (BER) | 193.3 | 100.2 ms | 51.8% | 1.38 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 193.3 | 89.24 ms | 46.2% | 1.66 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 219.4 | 115.47 ms | 52.6% | 1.41 ms | 0.04% | Fair |
| 🇯🇵 Tokyo (TYO) | 230 | 181.46 ms | 78.9% | 2.33 ms | 0.06% | Fair |
| 🇹🇼 Taipei (TPE) | 288.3 | 184.29 ms | 63.9% | 2.49 ms | 0% | High |
| ðŸ‡ðŸ‡° Hong Kong (HKG) | 301.5 | 176.86 ms | 58.7% | 2.99 ms | 0% | High |
| 🇦🇺 Sydney (SYD) | 303.1 | 131 ms | 43.2% | 2.46 ms | 0% | High |
| 🇦🇺 Melbourne (MEL) | 310.2 | 128.34 ms | 41.4% | 2.39 ms | 0% | High |
| 🇸🇬 Singapore (SIN) | 323.3 | 156.67 ms | 48.5% | 3.4 ms | 0.1% | High |
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 19 PoPs.
🇺🇸 Seattle Ping & Network Latency (SEA) | AS203314
Seattle (SEA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 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 18 Hats Network (AS203314) backbone PoPs.