# New York, USA → Amsterdam, Netherlands RTT

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

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

The 2026-08-16T04:07:28Z ICMP echo RTT run from New York, USA to Amsterdam, Netherlands averaged 68.7 ms over 50 samples, with a minimum of 66.97 ms and a maximum of 74.13 ms. Packet loss was zero, while the 1.38 ms standard deviation and 1.26 ms jitter place the route in the excellent latency tier.

The geodesic distance of 5,877.8 km gives a theoretical fiber-floor RTT of 57.56 ms, so the measured average is just 1.19x that floor. Fiber efficiency reaches 83.8%, meaning the route extracts most of the speed-of-light budget available across the Atlantic.

This route ranked 6th of 19 outbound routes in the network's measurement set. Its standard deviation relative to average RTT was 2.01%, below the 3.28% median for that set, so the low average is matched by unusually consistent behavior.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **68.7 ms**                                                  |
| Jitter               | **1.26 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **57.56 ms**                                                 |
| Fiber Efficiency     | **83.8%**                                                    |
| Latency Tier         | Excellent                                                    |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| Destination Region   | [Europe](/docs/network/latency/regions/europe)               |

## 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). 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        | **66.97 ms** |
| Average RTT        | **68.7 ms**  |
| Maximum RTT        | **74.13 ms** |
| Standard deviation | **1.38 ms**  |
| Stdev / average    | **2.0%**     |

## Route Context

* Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe)
* 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**

* [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms

**Fastest routes departing New York (NYC)**

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

**Fastest routes arriving at Amsterdam (AMS)**

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

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

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