🇺🇸 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.
🇺🇸 Seattle (SEA)
Seattle is the US Pacific Northwest's primary interconnection hub and a key landing point for trans-Pacific submarine cables to Japan and East Asia.
This page provides round-trip time (RTT) latency metrics between the Seattle (SEA) PoP and every other node on the Hats Network (AS203314) global backbone.
PoP Highlights
- Location: Seattle, USA (North America)
- Region: North America
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 5809844 — 47.60621, -122.33207
- Coverage: RTT measurements to 18 other PoPs across 4 continents
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇺🇸 Seattle (SEA) → 🇺🇸 Los Angeles (LAX) (27.1 ms) — Ultra-Low |
| Slowest Route | 🇺🇸 Seattle (SEA) → 🇦🇺 Melbourne (MEL) (172.6 ms) |
| Average RTT | 120.1 ms |
| Average Jitter | 0.98 ms |
| Average Packet Loss | 0.05% |
| Best Fiber Efficiency | 89.9% |
| Intra-Region Peers | 4 PoPs in North 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 Seattle (SEA)
Round-trip time in milliseconds from Seattle to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇺🇸 Los Angeles (LAX) | 27.1 | 15.12 ms | 55.8% | 0.26 ms | 0.11% | Ultra-Low |
| 🇺🇸 New York (NYC) | 59.1 | 37.95 ms | 64.2% | 0.34 ms | 0% | Excellent |
| 🇺🇸 Ashburn (IAD) | 61.8 | 36.27 ms | 58.7% | 0.62 ms | 0% | Excellent |
| 🇺🇸 Miami (MIA) | 81.1 | 43.08 ms | 53.1% | 0.52 ms | 0.09% | Good |
| 🇯🇵 Tokyo (TYO) | 84 | 75.55 ms | 89.9% | 0.92 ms | 0% | Good |
| 🇹🇼 Taipei (TPE) | 117.4 | 95.46 ms | 81.3% | 0.97 ms | 0% | Good |
| 🇬🇧 London (LON) | 124.3 | 75.63 ms | 60.8% | 0.63 ms | 0.11% | Good |
| 🇳🇱 Amsterdam (AMS) | 127.2 | 76.86 ms | 60.4% | 1.05 ms | 0% | Good |
| 🇭🇰 Hong Kong (HKG) | 128.6 | 102.2 ms | 79.5% | 1.29 ms | 0.03% | Good |
| 🇫🇷 Paris (PAR) | 130.3 | 78.98 ms | 60.6% | 1.29 ms | 0% | Good |
| 🇩🇪 Frankfurt (FRA) | 134.3 | 80.34 ms | 59.8% | 0.7 ms | 0.01% | Good |
| 🇩🇪 Berlin (BER) | 138.4 | 79.73 ms | 57.6% | 1.53 ms | 0.12% | Good |
| 🇫🇷 Marseille (MRS) | 139.5 | 85.27 ms | 61.1% | 0.64 ms | 0.09% | Good |
| 🇸🇬 Singapore (SIN) | 153.5 | 127.22 ms | 82.9% | 1 ms | 0.06% | Fair |
| 🇧🇷 São Paulo (GRU) | 155.1 | 106.76 ms | 68.8% | 1.24 ms | 0.07% | Fair |
| 🇦🇺 Sydney (SYD) | 162.7 | 121.96 ms | 75% | 1.47 ms | 0.15% | Fair |
| 🇷🇺 Moscow (MOW) | 164.1 | 82.23 ms | 50.1% | 1.62 ms | 0% | Fair |
| 🇦🇺 Melbourne (MEL) | 172.6 | 128.93 ms | 74.7% | 1.55 ms | 0% | Fair |
Inbound Latency to Seattle (SEA)
Round-trip time in milliseconds from all other PoPs to Seattle. 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 |
|---|---|---|---|---|---|---|
| 🇺🇸 Los Angeles (LAX) | 25.9 | 15.12 ms | 58.4% | 0.13 ms | 0% | Ultra-Low |
| 🇺🇸 New York (NYC) | 58.8 | 37.95 ms | 64.5% | 0.61 ms | 0.01% | Excellent |
| 🇺🇸 Ashburn (IAD) | 61.8 | 36.27 ms | 58.7% | 0.7 ms | 0% | Excellent |
| 🇺🇸 Miami (MIA) | 82.1 | 43.08 ms | 52.5% | 0.43 ms | 0% | Good |
| 🇯🇵 Tokyo (TYO) | 84.1 | 75.55 ms | 89.8% | 0.59 ms | 0.11% | Good |
| 🇹🇼 Taipei (TPE) | 115.5 | 95.46 ms | 82.6% | 0.54 ms | 0% | Good |
| 🇬🇧 London (LON) | 125.2 | 75.63 ms | 60.4% | 1.41 ms | 0% | Good |
| 🇳🇱 Amsterdam (AMS) | 128 | 76.86 ms | 60% | 1.09 ms | 0.19% | Good |
| 🇫🇷 Paris (PAR) | 129 | 78.98 ms | 61.2% | 1.02 ms | 0.09% | Good |
| 🇭🇰 Hong Kong (HKG) | 130.5 | 102.2 ms | 78.3% | 1.01 ms | 0.03% | Good |
| 🇩🇪 Frankfurt (FRA) | 133.1 | 80.34 ms | 60.4% | 1.41 ms | 0% | Good |
| 🇩🇪 Berlin (BER) | 138.7 | 79.73 ms | 57.5% | 1.03 ms | 0.13% | Good |
| 🇫🇷 Marseille (MRS) | 139.7 | 85.27 ms | 61% | 1.13 ms | 0.15% | Good |
| 🇸🇬 Singapore (SIN) | 153.8 | 127.22 ms | 82.7% | 1.42 ms | 0% | Fair |
| 🇧🇷 São Paulo (GRU) | 156.1 | 106.76 ms | 68.4% | 1.63 ms | 0.14% | Fair |
| 🇦🇺 Sydney (SYD) | 161.4 | 121.96 ms | 75.6% | 1.85 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 166.1 | 82.23 ms | 49.5% | 1.17 ms | 0% | Fair |
| 🇦🇺 Melbourne (MEL) | 172.2 | 128.93 ms | 74.9% | 1.52 ms | 0.04% | Fair |
North America Peers
Seattle is one of 5 Hats Network PoPs in North America. Intra-region routes offer the lowest latency and highest path diversity.
| PoP | Code | Country | RTT (ms) | Tier |
|---|---|---|---|---|
| 🇺🇸 Ashburn (IAD) | IAD | USA | 61.8 | Excellent |
| 🇺🇸 Los Angeles (LAX) | LAX | USA | 27.1 | Ultra-Low |
| 🇺🇸 Miami (MIA) | MIA | USA | 81.1 | Good |
| 🇺🇸 New York (NYC) | NYC | USA | 59.1 | Excellent |
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 19 PoPs.
🇺🇸 New York Ping & Network Latency (NYC) | AS203314
New York (NYC) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 18 Hats Network (AS203314) backbone PoPs.
🇧🇷 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.