πΊπΈ 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.
πΊπΈ 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.
Measurement round: 2026-08-15T04:03:13Z.
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.

Average RTT from Seattle 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 Seattle (SEA) 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) | 283.20 | 6.05 | 16,503 |
| Melbourne (MEL) | 171.40 | 5.88 | 13,166 |
| Moscow (MOW) | 164.60 | 5.43 | 8,397 |
| Sydney (SYD) | 162.50 | 3.43 | 12,454 |
| SΓ£o Paulo (GRU) | 155.10 | 7.50 | 10,902 |
| Singapore (SIN) | 153.60 | 4.22 | 12,991 |
| Marseille (MRS) | 139.30 | 4.75 | 8,707 |
| Berlin (BER) | 138.50 | 3.11 | 8,142 |
| Frankfurt (FRA) | 133.00 | 5.03 | 8,204 |
| Hong Kong (HKG) | 130.70 | 6.00 | 10,436 |
| Amsterdam (AMS) | 129.60 | 3.82 | 7,849 |
| Paris (PAR) | 128.10 | 5.98 | 8,065 |
| London (LON) | 125.20 | 2.99 | 7,723 |
| Taipei (TPE) | 115.10 | 2.99 | 9,748 |
| Tokyo (TYO) | 84.80 | 2.08 | 7,715 |
| Miami (MIA) | 81.10 | 3.95 | 4,399 |
| Ashburn (IAD) | 62.00 | 1.84 | 3,704 |
| New York (NYC) | 59.00 | 1.27 | 3,876 |
| Los Angeles (LAX) | 26.60 | 1.11 | 1,544 |
RTT vs. distance from Seattle
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 Seattle. 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) | 283.20 | 16,503 |
| Melbourne (MEL) | 171.40 | 13,166 |
| Moscow (MOW) | 164.60 | 8,397 |
| Sydney (SYD) | 162.50 | 12,454 |
| SΓ£o Paulo (GRU) | 155.10 | 10,902 |
| Singapore (SIN) | 153.60 | 12,991 |
| Marseille (MRS) | 139.30 | 8,707 |
| Berlin (BER) | 138.50 | 8,142 |
| Frankfurt (FRA) | 133.00 | 8,204 |
| Hong Kong (HKG) | 130.70 | 10,436 |
| Amsterdam (AMS) | 129.60 | 7,849 |
| Paris (PAR) | 128.10 | 8,065 |
| London (LON) | 125.20 | 7,723 |
| Taipei (TPE) | 115.10 | 9,748 |
| Tokyo (TYO) | 84.80 | 7,715 |
| Miami (MIA) | 81.10 | 4,399 |
| Ashburn (IAD) | 62.00 | 3,704 |
| New York (NYC) | 59.00 | 3,876 |
| Los Angeles (LAX) | 26.60 | 1,544 |
Fastest routes into Seattle
Measured RTT from 19 other PoPs into Seattle (SEA), 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 Seattle (SEA): 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 Seattle 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) |
|---|---|---|---|---|
| Los Angeles (LAX) | 27.50 | 26.34 | 30.47 | 1,544 |
| New York (NYC) | 59.00 | 56.09 | 69.10 | 3,876 |
| Ashburn (IAD) | 61.30 | 59.92 | 64.05 | 3,704 |
| Miami (MIA) | 82.00 | 79.01 | 90.39 | 4,399 |
| Tokyo (TYO) | 84.60 | 82.43 | 93.41 | 7,715 |
| Taipei (TPE) | 115.70 | 110.33 | 133.09 | 9,748 |
| London (LON) | 122.90 | 116.76 | 138.16 | 7,723 |
| Paris (PAR) | 127.20 | 122.19 | 138.01 | 8,065 |
| Hong Kong (HKG) | 129.90 | 127.66 | 139.63 | 10,436 |
| Amsterdam (AMS) | 130.10 | 127.89 | 135.67 | 7,849 |
| Frankfurt (FRA) | 134.00 | 128.47 | 150.15 | 8,204 |
| Berlin (BER) | 137.70 | 130.83 | 155.41 | 8,142 |
| Marseille (MRS) | 140.80 | 136.49 | 150.97 | 8,707 |
| Singapore (SIN) | 154.00 | 149.51 | 165.68 | 12,991 |
| SΓ£o Paulo (GRU) | 156.00 | 147.64 | 178.74 | 10,902 |
| Sydney (SYD) | 161.70 | 152.49 | 186.08 | 12,454 |
| Moscow (MOW) | 165.20 | 158.26 | 182.68 | 8,397 |
| Melbourne (MEL) | 169.50 | 163.18 | 185.11 | 13,166 |
| Johannesburg (JNB) | 280.90 | 273.88 | 303.39 | 16,503 |
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 19 other PoPs across 5 continents
Facility & Interconnection
- Facility: SEA1
- Upstream transit: HE / Cogent
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | πΊπΈ Seattle (SEA) β πΊπΈ Los Angeles (LAX) (26.6 ms) β Ultra-Low |
| Slowest Route | πΊπΈ Seattle (SEA) β πΏπ¦ Johannesburg (JNB) (283.2 ms) |
| Average RTT | 128.6 ms |
| Average Jitter | 1.07 ms |
| Average Packet Loss | 0.07% |
| Best Fiber Efficiency | 89.1% |
| Intra-Region Peers | 4 PoPs in North 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
Seattle sits on Hats Network's North America backbone. Measured round-trip times to its 4 intra-region peers range from 26.6 ms (Los Angeles (LAX)) to 81.1 ms (Miami (MIA)).
Seattle is the Pacific Northwest's primary interconnection hub and a landing point for trans-Pacific cables toward Japan and East Asia.
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) | 26.6 | 15.12 ms | 56.8% | 0.24 ms | 0.18% | Ultra-Low |
| πΊπΈ New York (NYC) | 59 | 37.95 ms | 64.3% | 0.54 ms | 0.16% | Excellent |
| πΊπΈ Ashburn (IAD) | 62 | 36.27 ms | 58.5% | 0.41 ms | 0.11% | Excellent |
| πΊπΈ Miami (MIA) | 81.1 | 43.08 ms | 53.1% | 0.91 ms | 0% | Good |
| π―π΅ Tokyo (TYO) | 84.8 | 75.55 ms | 89.1% | 0.86 ms | 0.05% | Good |
| πΉπΌ Taipei (TPE) | 115.1 | 95.46 ms | 82.9% | 1.19 ms | 0.17% | Good |
| π¬π§ London (LON) | 125.2 | 75.63 ms | 60.4% | 1.48 ms | 0.11% | Good |
| π«π· Paris (PAR) | 128.1 | 78.98 ms | 61.7% | 1.11 ms | 0.14% | Good |
| π³π± Amsterdam (AMS) | 129.6 | 76.86 ms | 59.3% | 1.02 ms | 0% | Good |
| ππ° Hong Kong (HKG) | 130.7 | 102.2 ms | 78.2% | 0.83 ms | 0.06% | Good |
| π©πͺ Frankfurt (FRA) | 133 | 80.34 ms | 60.4% | 0.69 ms | 0.04% | Good |
| π©πͺ Berlin (BER) | 138.5 | 79.73 ms | 57.6% | 0.97 ms | 0% | Good |
| π«π· Marseille (MRS) | 139.3 | 85.27 ms | 61.2% | 0.78 ms | 0.11% | Good |
| πΈπ¬ Singapore (SIN) | 153.6 | 127.22 ms | 82.8% | 1.43 ms | 0.02% | Fair |
| π§π· SΓ£o Paulo (GRU) | 155.1 | 106.76 ms | 68.8% | 1.4 ms | 0% | Fair |
| π¦πΊ Sydney (SYD) | 162.5 | 121.96 ms | 75.1% | 1.72 ms | 0.05% | Fair |
| π·πΊ Moscow (MOW) | 164.6 | 82.23 ms | 50% | 0.94 ms | 0.11% | Fair |
| π¦πΊ Melbourne (MEL) | 171.4 | 128.93 ms | 75.2% | 1.22 ms | 0.01% | Fair |
| πΏπ¦ Johannesburg (JNB) | 283.2 | 161.61 ms | 57.1% | 2.54 ms | 0% | High |
Fastest Routes to Seattle (SEA)
The 10 fastest measured routes to Seattle, 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 | πΊπΈ Los Angeles (LAX) | 27.5 ms | 26.34 ms | 30.47 ms | 1.05 ms |
| 2 | πΊπΈ New York (NYC) | 59 ms | 56.09 ms | 69.1 ms | 2.61 ms |
| 3 | πΊπΈ Ashburn (IAD) | 61.3 ms | 59.92 ms | 64.05 ms | 0.95 ms |
| 4 | πΊπΈ Miami (MIA) | 82 ms | 79.01 ms | 90.39 ms | 2.43 ms |
| 5 | π―π΅ Tokyo (TYO) | 84.6 ms | 82.43 ms | 93.41 ms | 1.91 ms |
| 6 | πΉπΌ Taipei (TPE) | 115.7 ms | 110.33 ms | 133.09 ms | 5.03 ms |
| 7 | π¬π§ London (LON) | 122.9 ms | 116.76 ms | 138.16 ms | 4.97 ms |
| 8 | π«π· Paris (PAR) | 127.2 ms | 122.19 ms | 138.01 ms | 4.05 ms |
| 9 | ππ° Hong Kong (HKG) | 129.9 ms | 127.66 ms | 139.63 ms | 2.28 ms |
| 10 | π³π± Amsterdam (AMS) | 130.1 ms | 127.89 ms | 135.67 ms | 1.97 ms |
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) | 27.5 | 15.12 ms | 55% | 0.3 ms | 0.12% | Ultra-Low |
| πΊπΈ New York (NYC) | 59 | 37.95 ms | 64.3% | 0.58 ms | 0% | Excellent |
| πΊπΈ Ashburn (IAD) | 61.3 | 36.27 ms | 59.2% | 0.55 ms | 0% | Excellent |
| πΊπΈ Miami (MIA) | 82 | 43.08 ms | 52.5% | 0.82 ms | 0% | Good |
| π―π΅ Tokyo (TYO) | 84.6 | 75.55 ms | 89.3% | 0.89 ms | 0% | Good |
| πΉπΌ Taipei (TPE) | 115.7 | 95.46 ms | 82.5% | 0.77 ms | 0% | Good |
| π¬π§ London (LON) | 122.9 | 75.63 ms | 61.5% | 1.4 ms | 0.13% | Good |
| π«π· Paris (PAR) | 127.2 | 78.98 ms | 62.1% | 1.18 ms | 0.11% | Good |
| ππ° Hong Kong (HKG) | 129.9 | 102.2 ms | 78.7% | 0.72 ms | 0.12% | Good |
| π³π± Amsterdam (AMS) | 130.1 | 76.86 ms | 59.1% | 1.14 ms | 0.11% | Good |
| π©πͺ Frankfurt (FRA) | 134 | 80.34 ms | 60% | 1.01 ms | 0% | Good |
| π©πͺ Berlin (BER) | 137.7 | 79.73 ms | 57.9% | 1.27 ms | 0.11% | Good |
| π«π· Marseille (MRS) | 140.8 | 85.27 ms | 60.6% | 1.18 ms | 0.04% | Good |
| πΈπ¬ Singapore (SIN) | 154 | 127.22 ms | 82.6% | 1.26 ms | 0.13% | Fair |
| π§π· SΓ£o Paulo (GRU) | 156 | 106.76 ms | 68.4% | 1.13 ms | 0.16% | Fair |
| π¦πΊ Sydney (SYD) | 161.7 | 121.96 ms | 75.4% | 1.24 ms | 0.04% | Fair |
| π·πΊ Moscow (MOW) | 165.2 | 82.23 ms | 49.8% | 0.92 ms | 0% | Fair |
| π¦πΊ Melbourne (MEL) | 169.5 | 128.93 ms | 76.1% | 1.16 ms | 0% | Fair |
| πΏπ¦ Johannesburg (JNB) | 280.9 | 161.61 ms | 57.5% | 3.2 ms | 0.08% | High |
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 | 62 | Excellent |
| πΊπΈ Los Angeles (LAX) | LAX | USA | 26.6 | Ultra-Low |
| πΊπΈ Miami (MIA) | MIA | USA | 81.1 | Good |
| πΊπΈ New York (NYC) | NYC | USA | 59 | Excellent |
Frequently Asked Questions
What is the fastest route to Seattle?
The fastest measured route to Seattle (SEA) is Los Angeles (LAX) β Seattle (SEA), averaging 27.5 ms RTT (Ultra-Low).
What is the fastest route from Seattle?
The fastest measured route from Seattle (SEA) is Seattle (SEA) β Los Angeles (LAX), averaging 26.6 ms RTT (Ultra-Low).
How well connected is Seattle to the Hats Network backbone?
Seattle (SEA) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, Seattle (SEA) β Johannesburg (JNB), averages 283.2 ms RTT.
Open Data
Measured latency data for Seattle (SEA) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:
- Per-route files β every directed route from Seattle is published as
sea-<destination>.pings.{csv,json,yaml}under/opendata/latency/latest/pairs/β for example sea-lax.pings.csv, the 50-probe ICMP echo round for Seattle (SEA) β Los Angeles (LAX). - 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.
πΊπΈ New York Ping & Network Latency (NYC) | AS203314
New York (NYC) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 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 19 Hats Network (AS203314) backbone PoPs.