# Amsterdam, Netherlands → Los Angeles, USA RTT

🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **Los Angeles, USA (LAX)**

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

For round 2026-08-16T04:07:28Z, ICMP echo RTT from Amsterdam, Netherlands to Los Angeles, USA averaged 133.7 ms over 50 samples; the minimum was 130.58 ms and the maximum was 141.4 ms. No packets were lost, and the 2.49 ms standard deviation produced 2.11 ms jitter, so the long distance did not translate into erratic round-trip times.

At 1.52 times the 87.74 ms fiber floor for the 8,960 km great-circle distance, the route has 65.6% straight-line fiber efficiency and a 59.77 ms vacuum floor. The measured RTT stays within a 10.8 ms band even though the destination is nearly 9,000 km away, making the tight spread the most distinctive feature of this route.

Average latency ranks 11th among the 19 outbound routes measured from Amsterdam. Variability of about 1.9% is much lower than the 3.28% median variability across the route set, which makes the 133.7 ms average a dependable reference for this coastal destination.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **133.7 ms**                                                 |
| Jitter               | **2.11 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **87.74 ms**                                                 |
| Fiber Efficiency     | **65.6%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [Europe](/docs/network/latency/regions/europe)               |
| Destination Region   | [North America](/docs/network/latency/regions/north-america) |

## Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

## Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) and [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address.

| Physical Reference                            | Value         |
| --------------------------------------------- | ------------- |
| WGS-84 geodesic distance                      | **8,960 km**  |
| Vacuum RTT floor                              | **59.77 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **87.74 ms**  |
| Low-latency fiber material floor              | **87.39 ms**  |
| Engineering floor (5% path allowance)         | **92.14 ms**  |
| Research 1.33× mapped-fiber reference         | **116.7 ms**  |
| Estimated unamplified path loss               | **1881.6 dB** |
| Transparent optical spans / inline amplifiers | **118 / 117** |
| Published RTT inflation over fiber floor      | **1.52×**     |

Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency).

## Stability & Trend

The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

| Round Statistic    | Value         |
| ------------------ | ------------- |
| Minimum RTT        | **130.58 ms** |
| Average RTT        | **133.7 ms**  |
| Maximum RTT        | **141.4 ms**  |
| Standard deviation | **2.49 ms**   |
| Stdev / average    | **1.9%**      |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america)
* Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Los Angeles to Amsterdam latency and RTT](/docs/network/latency/pairs/lax-ams-rtt) — 132.1 ms

**Fastest routes departing Amsterdam (AMS)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms
* [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms
* [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms

**Fastest routes arriving at Los Angeles (LAX)**

* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms
* [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms
* [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms
* [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms

**Same corridor (Europe → North America)**

* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms
* [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms
* [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms

## About This Measurement

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/ams-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Los Angeles round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/ams-lax-rtt).
- **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.