# 🇺🇸 Los Angeles Ping & Network Latency (LAX) | AS203314

## 🇺🇸 Los Angeles (LAX)

Los Angeles is the primary US West Coast gateway to the Asia-Pacific region, landing major trans-Pacific submarine cables. Hats Network's LA PoP provides the lowest-latency path to East Asia.

Measurement round: `2026-08-16T04:07:28Z`.

This page provides round-trip time (RTT) latency metrics between the **Los Angeles (LAX)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Los Angeles, USA (North America)
* **Region:** North America
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 5368361](https://www.geonames.org/5368361) — 34.05223, -118.24368
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** LAX1
* **Upstream transit:** HE / Cogent / Comcast

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                            |
| --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇺🇸 Los Angeles (LAX) → 🇺🇸 Seattle (SEA)](/docs/network/latency/pairs/lax-sea-rtt) (**26.9 ms**) — Ultra-Low |
| Slowest Route         | [🇺🇸 Los Angeles (LAX) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/lax-jnb-rtt) (**287.2 ms**)       |
| Average RTT           | **129.2 ms**                                                                                                     |
| Average Jitter        | **1.03 ms**                                                                                                      |
| Average Packet Loss   | **0.04%**                                                                                                        |
| Best Fiber Efficiency | **85.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

Los Angeles sits on Hats Network's **North America** backbone. Measured round-trip times to its 4 intra-region peers range from **26.9 ms** (Seattle (SEA)) to **60.4 ms** (Ashburn (IAD)).

Los Angeles is the primary US West Coast landing point for trans-Pacific submarine cables, giving the backbone its shortest Pacific crossing toward East Asia.

## Outbound Latency from Los Angeles (LAX)

Round-trip time in milliseconds **from Los Angeles** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇺🇸 Seattle (SEA)      | **[26.9](/docs/network/latency/pairs/lax-sea-rtt)**  | 15.12 ms    | 56.2%      | 0.3 ms  | 0.13% | Ultra-Low |
| 🇺🇸 Miami (MIA)        | **[57.3](/docs/network/latency/pairs/lax-mia-rtt)**  | 36.86 ms    | 64.3%      | 0.34 ms | 0%    | Excellent |
| 🇺🇸 New York (NYC)     | **[57.9](/docs/network/latency/pairs/lax-nyc-rtt)**  | 38.63 ms    | 66.7%      | 0.34 ms | 0.09% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[60.4](/docs/network/latency/pairs/lax-iad-rtt)**  | 35.84 ms    | 59.3%      | 0.64 ms | 0.06% | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[101.2](/docs/network/latency/pairs/lax-tyo-rtt)** | 86.51 ms    | 85.5%      | 0.82 ms | 0%    | Good      |
| 🇬🇧 London (LON)       | **[129.2](/docs/network/latency/pairs/lax-lon-rtt)** | 85.95 ms    | 66.5%      | 1.17 ms | 0%    | Good      |
| 🇧🇷 São Paulo (GRU)    | **[131.3](/docs/network/latency/pairs/lax-gru-rtt)** | 96.89 ms    | 73.8%      | 0.87 ms | 0%    | Good      |
| 🇳🇱 Amsterdam (AMS)    | **[132.1](/docs/network/latency/pairs/lax-ams-rtt)** | 87.74 ms    | 66.4%      | 0.78 ms | 0%    | Good      |
| 🇹🇼 Taipei (TPE)       | **[132.9](/docs/network/latency/pairs/lax-tpe-rtt)** | 107 ms      | 80.5%      | 0.87 ms | 0.08% | Good      |
| 🇫🇷 Paris (PAR)        | **[135.9](/docs/network/latency/pairs/lax-par-rtt)** | 89.18 ms    | 65.6%      | 0.62 ms | 0%    | Good      |
| 🇦🇺 Sydney (SYD)       | **[137.6](/docs/network/latency/pairs/lax-syd-rtt)** | 118.13 ms   | 85.9%      | 1.65 ms | 0%    | Good      |
| 🇩🇪 Berlin (BER)       | **[139.3](/docs/network/latency/pairs/lax-ber-rtt)** | 91.39 ms    | 65.6%      | 1.58 ms | 0.12% | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[142.3](/docs/network/latency/pairs/lax-fra-rtt)** | 91.31 ms    | 64.2%      | 0.71 ms | 0%    | Good      |
| 🇫🇷 Marseille (MRS)    | **[143.9](/docs/network/latency/pairs/lax-mrs-rtt)** | 95.09 ms    | 66.1%      | 1.05 ms | 0.16% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[146.5](/docs/network/latency/pairs/lax-hkg-rtt)** | 114.3 ms    | 78%        | 1.42 ms | 0%    | Good      |
| 🇦🇺 Melbourne (MEL)    | **[148.2](/docs/network/latency/pairs/lax-mel-rtt)** | 125 ms      | 84.3%      | 1.74 ms | 0.06% | Good      |
| 🇸🇬 Singapore (SIN)    | **[167.7](/docs/network/latency/pairs/lax-sin-rtt)** | 138.43 ms   | 82.5%      | 1.33 ms | 0%    | Fair      |
| 🇷🇺 Moscow (MOW)       | **[177](/docs/network/latency/pairs/lax-mow-rtt)**   | 95.9 ms     | 54.2%      | 1.7 ms  | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[287.2](/docs/network/latency/pairs/lax-jnb-rtt)** | 163.35 ms   | 56.9%      | 1.6 ms  | 0.08% | High      |

## Fastest Routes to Los Angeles (LAX)

The 10 fastest measured routes **to Los Angeles**, 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    | 🇺🇸 Seattle (SEA)   | **[25.9 ms](/docs/network/latency/pairs/sea-lax-rtt)**  | 25.44 ms  | 27.56 ms  | 0.42 ms |
| 2    | 🇺🇸 Miami (MIA)     | **[56.8 ms](/docs/network/latency/pairs/mia-lax-rtt)**  | 54.44 ms  | 64.31 ms  | 2.11 ms |
| 3    | 🇺🇸 New York (NYC)  | **[58.9 ms](/docs/network/latency/pairs/nyc-lax-rtt)**  | 56.67 ms  | 64.24 ms  | 2.02 ms |
| 4    | 🇺🇸 Ashburn (IAD)   | **[60.7 ms](/docs/network/latency/pairs/iad-lax-rtt)**  | 58.56 ms  | 67.73 ms  | 1.84 ms |
| 5    | 🇯🇵 Tokyo (TYO)     | **[101.2 ms](/docs/network/latency/pairs/tyo-lax-rtt)** | 98.89 ms  | 105.47 ms | 1.62 ms |
| 6    | 🇬🇧 London (LON)    | **[127.5 ms](/docs/network/latency/pairs/lon-lax-rtt)** | 123.84 ms | 138.75 ms | 3.03 ms |
| 7    | 🇧🇷 São Paulo (GRU) | **[130.8 ms](/docs/network/latency/pairs/gru-lax-rtt)** | 125.52 ms | 141.14 ms | 3.75 ms |
| 8    | 🇹🇼 Taipei (TPE)    | **[132 ms](/docs/network/latency/pairs/tpe-lax-rtt)**   | 129.33 ms | 144.07 ms | 2.56 ms |
| 9    | 🇳🇱 Amsterdam (AMS) | **[133.7 ms](/docs/network/latency/pairs/ams-lax-rtt)** | 130.58 ms | 141.4 ms  | 2.49 ms |
| 10   | 🇫🇷 Paris (PAR)     | **[136.5 ms](/docs/network/latency/pairs/par-lax-rtt)** | 130.92 ms | 152.23 ms | 5.13 ms |

## Inbound Latency to Los Angeles (LAX)

Round-trip time in milliseconds **from all other PoPs to Los Angeles**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇺🇸 Seattle (SEA)      | **[25.9](/docs/network/latency/pairs/sea-lax-rtt)**  | 15.12 ms    | 58.4%      | 0.24 ms | 0%    | Ultra-Low |
| 🇺🇸 Miami (MIA)        | **[56.8](/docs/network/latency/pairs/mia-lax-rtt)**  | 36.86 ms    | 64.9%      | 0.59 ms | 0%    | Excellent |
| 🇺🇸 New York (NYC)     | **[58.9](/docs/network/latency/pairs/nyc-lax-rtt)**  | 38.63 ms    | 65.6%      | 0.46 ms | 0%    | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[60.7](/docs/network/latency/pairs/iad-lax-rtt)**  | 35.84 ms    | 59%        | 0.32 ms | 0%    | Excellent |
| 🇯🇵 Tokyo (TYO)        | **[101.2](/docs/network/latency/pairs/tyo-lax-rtt)** | 86.51 ms    | 85.5%      | 0.97 ms | 0.02% | Good      |
| 🇬🇧 London (LON)       | **[127.5](/docs/network/latency/pairs/lon-lax-rtt)** | 85.95 ms    | 67.4%      | 0.86 ms | 0.17% | Good      |
| 🇧🇷 São Paulo (GRU)    | **[130.8](/docs/network/latency/pairs/gru-lax-rtt)** | 96.89 ms    | 74.1%      | 0.66 ms | 0%    | Good      |
| 🇹🇼 Taipei (TPE)       | **[132](/docs/network/latency/pairs/tpe-lax-rtt)**   | 107 ms      | 81.1%      | 1.31 ms | 0%    | Good      |
| 🇳🇱 Amsterdam (AMS)    | **[133.7](/docs/network/latency/pairs/ams-lax-rtt)** | 87.74 ms    | 65.6%      | 0.65 ms | 0%    | Good      |
| 🇫🇷 Paris (PAR)        | **[136.5](/docs/network/latency/pairs/par-lax-rtt)** | 89.18 ms    | 65.3%      | 1.58 ms | 0.11% | Good      |
| 🇦🇺 Sydney (SYD)       | **[136.5](/docs/network/latency/pairs/syd-lax-rtt)** | 118.13 ms   | 86.5%      | 1.54 ms | 0.12% | Good      |
| 🇩🇪 Berlin (BER)       | **[140.9](/docs/network/latency/pairs/ber-lax-rtt)** | 91.39 ms    | 64.9%      | 1.62 ms | 0.1%  | Good      |
| 🇩🇪 Frankfurt (FRA)    | **[141.8](/docs/network/latency/pairs/fra-lax-rtt)** | 91.31 ms    | 64.4%      | 1.06 ms | 0%    | Good      |
| 🇫🇷 Marseille (MRS)    | **[144.5](/docs/network/latency/pairs/mrs-lax-rtt)** | 95.09 ms    | 65.8%      | 0.78 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[145](/docs/network/latency/pairs/hkg-lax-rtt)**   | 114.3 ms    | 78.8%      | 1.4 ms  | 0.06% | Good      |
| 🇦🇺 Melbourne (MEL)    | **[148.4](/docs/network/latency/pairs/mel-lax-rtt)** | 125 ms      | 84.2%      | 1.28 ms | 0.07% | Good      |
| 🇸🇬 Singapore (SIN)    | **[168.2](/docs/network/latency/pairs/sin-lax-rtt)** | 138.43 ms   | 82.3%      | 1.78 ms | 0.03% | Fair      |
| 🇷🇺 Moscow (MOW)       | **[177.7](/docs/network/latency/pairs/mow-lax-rtt)** | 95.9 ms     | 54%        | 1.55 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[285.5](/docs/network/latency/pairs/jnb-lax-rtt)** | 163.35 ms   | 57.2%      | 2.14 ms | 0.01% | High      |

## North America Peers

Los Angeles 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     | **60.4** | Excellent |
| [🇺🇸 Miami (MIA)](./mia-miami)       | MIA  | USA     | **57.3** | Excellent |
| [🇺🇸 New York (NYC)](./nyc-new-york) | NYC  | USA     | **57.9** | Excellent |
| [🇺🇸 Seattle (SEA)](./sea-seattle)   | SEA  | USA     | **26.9** | Ultra-Low |

## Frequently Asked Questions

**What is the fastest route to Los Angeles?**

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

**What is the fastest route from Los Angeles?**

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

**How well connected is Los Angeles to the Hats Network backbone?**

Los Angeles (LAX) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Los Angeles (LAX) → Johannesburg (JNB)](/docs/network/latency/pairs/lax-jnb-rtt), averages **287.2 ms** RTT.

## Open Data

Measured latency data for Los Angeles (LAX) 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 Los Angeles is published as `lax-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [lax-sea.pings.csv](/opendata/latency/latest/pairs/lax-sea.pings.csv), the 50-probe ICMP echo round for [Los Angeles (LAX) → Seattle (SEA)](/docs/network/latency/pairs/lax-sea-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/lax-los-angeles).
- **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.