# 🇺🇸 Seattle Ping & Network Latency (SEA) | AS203314

## 🇺🇸 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-16T04:07:28Z`.

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](https://www.geonames.org/5809844) — 47.60621, -122.33207
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** SEA1
* **Upstream transit:** HE / Cogent

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                            |
| --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇺🇸 Seattle (SEA) → 🇺🇸 Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt) (**25.9 ms**) — Ultra-Low |
| Slowest Route         | [🇺🇸 Seattle (SEA) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/sea-jnb-rtt) (**282.1 ms**)           |
| Average RTT           | **128.5 ms**                                                                                                     |
| Average Jitter        | **1.09 ms**                                                                                                      |
| Average Packet Loss   | **0.03%**                                                                                                        |
| Best Fiber Efficiency | **88.9%**                                                                                                        |
| 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](/docs/network/latency/theoretical-fiber-latency).

## Geographic & Network Position

Seattle sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **25.9 ms** (Los Angeles (LAX)) to **81.7 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)  | **[25.9](/docs/network/latency/pairs/sea-lax-rtt)**  | 15.12 ms    | 58.4%      | 0.24 ms | 0%    | Ultra-Low |
| 🇺🇸 New York (NYC)     | **[59.5](/docs/network/latency/pairs/sea-nyc-rtt)**  | 37.95 ms    | 63.8%      | 0.66 ms | 0.16% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[61.5](/docs/network/latency/pairs/sea-iad-rtt)**  | 36.27 ms    | 59%        | 0.55 ms | 0%    | Excellent |
| 🇺🇸 Miami (MIA)        | **[81.7](/docs/network/latency/pairs/sea-mia-rtt)**  | 43.08 ms    | 52.7%      | 0.84 ms | 0%    | Good      |
| 🇯🇵 Tokyo (TYO)        | **[85](/docs/network/latency/pairs/sea-tyo-rtt)**    | 75.55 ms    | 88.9%      | 0.39 ms | 0%    | Good      |
| 🇹🇼 Taipei (TPE)       | **[114.7](/docs/network/latency/pairs/sea-tpe-rtt)** | 95.46 ms    | 83.2%      | 1.36 ms | 0%    | Good      |
| 🇬🇧 London (LON)       | **[124.1](/docs/network/latency/pairs/sea-lon-rtt)** | 75.63 ms    | 60.9%      | 1.38 ms | 0%    | Good      |
| 🇳🇱 Amsterdam (AMS)    | **[128.6](/docs/network/latency/pairs/sea-ams-rtt)** | 76.86 ms    | 59.8%      | 1.46 ms | 0.13% | Good      |
| 🇫🇷 Paris (PAR)        | **[129.2](/docs/network/latency/pairs/sea-par-rtt)** | 78.98 ms    | 61.1%      | 1.22 ms | 0.02% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[130.4](/docs/network/latency/pairs/sea-hkg-rtt)** | 102.2 ms    | 78.4%      | 0.7 ms  | 0%    | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[133.2](/docs/network/latency/pairs/sea-fra-rtt)** | 80.34 ms    | 60.3%      | 0.66 ms | 0.11% | Good      |
| 🇩🇪 Berlin (BER)       | **[140.9](/docs/network/latency/pairs/sea-ber-rtt)** | 79.73 ms    | 56.6%      | 1.36 ms | 0.01% | Good      |
| 🇫🇷 Marseille (MRS)    | **[141.2](/docs/network/latency/pairs/sea-mrs-rtt)** | 85.27 ms    | 60.4%      | 1.25 ms | 0.04% | Good      |
| 🇸🇬 Singapore (SIN)    | **[151.1](/docs/network/latency/pairs/sea-sin-rtt)** | 127.22 ms   | 84.2%      | 1.4 ms  | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[155.7](/docs/network/latency/pairs/sea-gru-rtt)** | 106.76 ms   | 68.6%      | 1.76 ms | 0%    | Fair      |
| 🇦🇺 Sydney (SYD)       | **[161.3](/docs/network/latency/pairs/sea-syd-rtt)** | 121.96 ms   | 75.6%      | 1.49 ms | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[164.6](/docs/network/latency/pairs/sea-mow-rtt)** | 82.23 ms    | 50%        | 1.42 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[170.1](/docs/network/latency/pairs/sea-mel-rtt)** | 128.93 ms   | 75.8%      | 0.98 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[282.1](/docs/network/latency/pairs/sea-jnb-rtt)** | 161.61 ms   | 57.3%      | 1.53 ms | 0.15% | 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) | **[26.9 ms](/docs/network/latency/pairs/lax-sea-rtt)**  | 25.5 ms   | 29.88 ms  | 1.13 ms |
| 2    | 🇺🇸 New York (NYC)    | **[58.7 ms](/docs/network/latency/pairs/nyc-sea-rtt)**  | 56.64 ms  | 67.85 ms  | 2.09 ms |
| 3    | 🇺🇸 Ashburn (IAD)     | **[62.3 ms](/docs/network/latency/pairs/iad-sea-rtt)**  | 59.37 ms  | 75.24 ms  | 2.67 ms |
| 4    | 🇺🇸 Miami (MIA)       | **[81.9 ms](/docs/network/latency/pairs/mia-sea-rtt)**  | 78.54 ms  | 93.5 ms   | 3.48 ms |
| 5    | 🇯🇵 Tokyo (TYO)       | **[84.8 ms](/docs/network/latency/pairs/tyo-sea-rtt)**  | 81.06 ms  | 94.31 ms  | 2.93 ms |
| 6    | 🇹🇼 Taipei (TPE)      | **[115.8 ms](/docs/network/latency/pairs/tpe-sea-rtt)** | 111.75 ms | 128.63 ms | 4.07 ms |
| 7    | 🇬🇧 London (LON)      | **[123.2 ms](/docs/network/latency/pairs/lon-sea-rtt)** | 121.09 ms | 129.68 ms | 1.95 ms |
| 8    | 🇫🇷 Paris (PAR)       | **[128 ms](/docs/network/latency/pairs/par-sea-rtt)**   | 123.76 ms | 137.5 ms  | 3.51 ms |
| 9    | 🇳🇱 Amsterdam (AMS)   | **[130.2 ms](/docs/network/latency/pairs/ams-sea-rtt)** | 123.59 ms | 144.11 ms | 5.22 ms |
| 10   | 🇭🇰 Hong Kong (HKG)   | **[131.6 ms](/docs/network/latency/pairs/hkg-sea-rtt)** | 125.78 ms | 162.34 ms | 6.2 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)  | **[26.9](/docs/network/latency/pairs/lax-sea-rtt)**  | 15.12 ms    | 56.2%      | 0.3 ms  | 0.13% | Ultra-Low |
| 🇺🇸 New York (NYC)     | **[58.7](/docs/network/latency/pairs/nyc-sea-rtt)**  | 37.95 ms    | 64.7%      | 0.35 ms | 0.11% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[62.3](/docs/network/latency/pairs/iad-sea-rtt)**  | 36.27 ms    | 58.2%      | 0.44 ms | 0.12% | Excellent |
| 🇺🇸 Miami (MIA)        | **[81.9](/docs/network/latency/pairs/mia-sea-rtt)**  | 43.08 ms    | 52.6%      | 0.47 ms | 0.1%  | Good      |
| 🇯🇵 Tokyo (TYO)        | **[84.8](/docs/network/latency/pairs/tyo-sea-rtt)**  | 75.55 ms    | 89.1%      | 0.77 ms | 0.06% | Good      |
| 🇹🇼 Taipei (TPE)       | **[115.8](/docs/network/latency/pairs/tpe-sea-rtt)** | 95.46 ms    | 82.4%      | 0.97 ms | 0.15% | Good      |
| 🇬🇧 London (LON)       | **[123.2](/docs/network/latency/pairs/lon-sea-rtt)** | 75.63 ms    | 61.4%      | 0.95 ms | 0%    | Good      |
| 🇫🇷 Paris (PAR)        | **[128](/docs/network/latency/pairs/par-sea-rtt)**   | 78.98 ms    | 61.7%      | 0.85 ms | 0.07% | Good      |
| 🇳🇱 Amsterdam (AMS)    | **[130.2](/docs/network/latency/pairs/ams-sea-rtt)** | 76.86 ms    | 59%        | 1.26 ms | 0.04% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[131.6](/docs/network/latency/pairs/hkg-sea-rtt)** | 102.2 ms    | 77.7%      | 0.82 ms | 0.05% | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[135.2](/docs/network/latency/pairs/fra-sea-rtt)** | 80.34 ms    | 59.4%      | 0.98 ms | 0.16% | Good      |
| 🇩🇪 Berlin (BER)       | **[139.7](/docs/network/latency/pairs/ber-sea-rtt)** | 79.73 ms    | 57.1%      | 1.63 ms | 0.2%  | Good      |
| 🇫🇷 Marseille (MRS)    | **[141.7](/docs/network/latency/pairs/mrs-sea-rtt)** | 85.27 ms    | 60.2%      | 1.19 ms | 0.12% | Good      |
| 🇸🇬 Singapore (SIN)    | **[151.5](/docs/network/latency/pairs/sin-sea-rtt)** | 127.22 ms   | 84%        | 1.11 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[155.9](/docs/network/latency/pairs/gru-sea-rtt)** | 106.76 ms   | 68.5%      | 1.54 ms | 0.19% | Fair      |
| 🇦🇺 Sydney (SYD)       | **[161.9](/docs/network/latency/pairs/syd-sea-rtt)** | 121.96 ms   | 75.3%      | 1.74 ms | 0.03% | Fair      |
| 🇷🇺 Moscow (MOW)       | **[164.8](/docs/network/latency/pairs/mow-sea-rtt)** | 82.23 ms    | 49.9%      | 0.99 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[172.1](/docs/network/latency/pairs/mel-sea-rtt)** | 128.93 ms   | 74.9%      | 1.49 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[281.2](/docs/network/latency/pairs/jnb-sea-rtt)** | 161.61 ms   | 57.5%      | 1.91 ms | 0.11% | 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-ashburn)         | IAD  | USA     | **61.5** | Excellent |
| [🇺🇸 Los Angeles (LAX)](./lax-los-angeles) | LAX  | USA     | **25.9** | Ultra-Low |
| [🇺🇸 Miami (MIA)](./mia-miami)             | MIA  | USA     | **81.7** | Good      |
| [🇺🇸 New York (NYC)](./nyc-new-york)       | NYC  | USA     | **59.5** | Excellent |

## Frequently Asked Questions

**What is the fastest route to Seattle?**

The fastest measured route to Seattle (SEA) is [Los Angeles (LAX) → Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt), averaging **26.9 ms** RTT (Ultra-Low).

**What is the fastest route from Seattle?**

The fastest measured route from Seattle (SEA) is [Seattle (SEA) → Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt), averaging **25.9 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)](/docs/network/latency/pairs/sea-jnb-rtt), averages **282.1 ms** RTT.

## Open Data

Measured latency data for Seattle (SEA) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/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/`](/opendata/latency/latest/pairs/) — for example [sea-lax.pings.csv](/opendata/latency/latest/pairs/sea-lax.pings.csv), the 50-probe ICMP echo round for [Seattle (SEA) → Los Angeles (LAX)](/docs/network/latency/pairs/sea-lax-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/sea-seattle).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.