# Amsterdam, Netherlands → New York, USA RTT

🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇺🇸 **New York, USA (NYC)**

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

For the ICMP RTT round at 2026-08-16T04:07:28Z, 50 echo requests from Amsterdam, Netherlands to New York, USA returned an average round-trip time of 68.6 ms, with a minimum of 67.28 ms and a maximum of 73 ms.

The path was very stable: standard deviation was 1.16 ms, jitter was 1.05 ms, and every packet arrived, so no packet loss was observed. In the context of the 19 outbound routes measured from Amsterdam in this round, this route ranked 7th by average latency. Its standard deviation is about 1.7% of its average, tighter than the median route's 3.28% ratio, confirming that the transatlantic connection is not only quick but also consistent.

The physical reference for this route is a geodesic distance of 5,877.8 km, giving a vacuum floor of 39.21 ms and a fiber floor of 57.56 ms. The measured 68.6 ms average sits 1.19 times above the fiber floor, or about 83.9% fiber efficiency, meaning the path adds roughly 11 ms beyond the best-case fiber transit time.

With no loss and a 1.05 ms jitter, this route provides a clean network-layer reference for repeated ICMP round-trip checks across the Atlantic.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **68.6 ms**                                                  |
| Jitter               | **1.05 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **57.56 ms**                                                 |
| Fiber Efficiency     | **83.9%**                                                    |
| Latency Tier         | Excellent                                                    |
| 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **5,877.8 km** |
| Vacuum RTT floor                              | **39.21 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **57.56 ms**   |
| Low-latency fiber material floor              | **57.33 ms**   |
| Engineering floor (5% path allowance)         | **60.45 ms**   |
| Research 1.33× mapped-fiber reference         | **76.56 ms**   |
| Estimated unamplified path loss               | **1234.3 dB**  |
| Transparent optical spans / inline amplifiers | **78 / 77**    |
| Published RTT inflation over fiber floor      | **1.19×**      |

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        | **67.28 ms** |
| Average RTT        | **68.6 ms**  |
| Maximum RTT        | **73 ms**    |
| Standard deviation | **1.16 ms**  |
| Stdev / average    | **1.7%**     |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* 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**

* [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 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 New York (NYC)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms

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

* [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms
* [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-rtt) — 71 ms
* [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 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-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → New York 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-nyc-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.