New York, USA → Amsterdam, Netherlands RTT
ICMP RTT measurement from New York, USA to Amsterdam, Netherlands: average 68.7 ms, min/max latency, jitter, packet loss, and route efficiency.
🇺🇸 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 |
| Destination Region | 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.
Ping series: NYC → AMS
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 68.7 ± 0.20 ms (SE)
Sample distribution: box = interquartile range (67.7–69.1 ms), median 68.5 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (57.6 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 69.05 |
| 2 | 100 | 67.71 |
| 3 | 200 | 67.23 |
| 4 | 300 | 69.10 |
| 5 | 400 | 68.13 |
| 6 | 500 | 68.90 |
| 7 | 600 | 70.38 |
| 8 | 700 | 68.68 |
| 9 | 800 | 68.10 |
| 10 | 900 | 67.50 |
| 11 | 1000 | 67.79 |
| 12 | 1100 | 67.60 |
| 13 | 1200 | 67.23 |
| 14 | 1300 | 66.97 |
| 15 | 1400 | 70.20 |
| 16 | 1500 | 74.13 |
| 17 | 1600 | 70.24 |
| 18 | 1700 | 68.67 |
| 19 | 1800 | 67.83 |
| 20 | 1900 | 67.50 |
| 21 | 2000 | 67.17 |
| 22 | 2100 | 66.99 |
| 23 | 2200 | 67.41 |
| 24 | 2300 | 68.19 |
| 25 | 2400 | 71.04 |
| 26 | 2500 | 69.13 |
| 27 | 2600 | 67.92 |
| 28 | 2700 | 68.57 |
| 29 | 2800 | 68.23 |
| 30 | 2900 | 70.74 |
| 31 | 3000 | 69.67 |
| 32 | 3100 | 68.41 |
| 33 | 3200 | 68.53 |
| 34 | 3300 | 67.43 |
| 35 | 3400 | 69.07 |
| 36 | 3500 | 68.20 |
| 37 | 3600 | 70.40 |
| 38 | 3700 | 68.23 |
| 39 | 3800 | 67.32 |
| 40 | 3900 | 69.22 |
| 41 | 4000 | 68.66 |
| 42 | 4100 | 67.95 |
| 43 | 4200 | 68.84 |
| 44 | 4300 | 67.68 |
| 45 | 4400 | 67.49 |
| 46 | 4500 | 71.94 |
| 47 | 4600 | 68.66 |
| 48 | 4700 | 69.09 |
| 49 | 4800 | 69.64 |
| 50 | 4900 | 70.24 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for New York City (40.71427, -74.00597) and Amsterdam (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 () | 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.
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% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 68.8 ms
- Minimum
- 68.1 ms
- Maximum
- 69.4 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: New York (NYC)
- Destination PoP: Amsterdam (AMS)
- Region overview: North America → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Amsterdam to New York latency and RTT — 68.6 ms
Fastest routes departing New York (NYC)
- New York to Ashburn latency and RTT — 6 ms
- New York to Miami latency and RTT — 32.9 ms
- New York to Seattle latency and RTT — 58.7 ms
- New York to Los Angeles latency and RTT — 58.9 ms
- New York to London latency and RTT — 63.5 ms
Fastest routes arriving at Amsterdam (AMS)
- London to Amsterdam latency and RTT — 5.2 ms
- Frankfurt to Amsterdam latency and RTT — 5.9 ms
- Paris to Amsterdam latency and RTT — 7 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Marseille to Amsterdam latency and RTT — 20.3 ms
Same corridor (North America → Europe)
- New York to Paris latency and RTT — 68.9 ms
- Ashburn to London latency and RTT — 70.3 ms
- New York to Frankfurt latency and 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. 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 or browse more city-pair routes.