Amsterdam, Netherlands → Ashburn, USA RTT
ICMP round-trip latency from Amsterdam, Netherlands to Ashburn, USA: measured average, minimum, maximum, jitter, and packet loss for the Amsterdam–Ashburn route
🇳🇱 Amsterdam, Netherlands (AMS) → 🇺🇸 Ashburn, USA (IAD)
Measurement round: 2026-08-15T04:03:13Z.
In the 2026-08-15T04:03:13Z measurement round, the Amsterdam-to-Ashburn ICMP echo route averaged 75.7 ms round-trip time across 50 samples, with a minimum of 71.94 ms, a maximum of 87.08 ms, and no packet loss.
The 3.2 ms standard deviation and 2.62 ms jitter keep the RTT spread tight, and the average sits at 1.24 times the theoretical fiber floor for the 6,223 km distance, an 80.5% fiber efficiency figure. It remains within the Excellent latency tier.
Ranked 8th among the 19 Amsterdam outbound routes in this round, this path shows variation of roughly 4.2% of its average RTT, above the 3.08% median variation across those routes. Even so, the zero-loss sample and narrow absolute jitter make it a notably direct and steady transatlantic route.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 75.7 ms |
| Jitter | 2.62 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 60.94 ms |
| Fiber Efficiency | 80.5% |
| Latency Tier | Excellent |
| Source Region | Europe |
| Destination Region | 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.
Ping series: AMS → IAD
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 75.7 ± 0.45 ms (SE)
Sample distribution: box = interquartile range (73.4–77.3 ms), median 74.8 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 (60.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 71.94 |
| 2 | 100 | 71.95 |
| 3 | 200 | 72.12 |
| 4 | 300 | 72.40 |
| 5 | 400 | 78.16 |
| 6 | 500 | 74.13 |
| 7 | 600 | 72.88 |
| 8 | 700 | 77.42 |
| 9 | 800 | 75.43 |
| 10 | 900 | 74.94 |
| 11 | 1000 | 74.26 |
| 12 | 1100 | 75.24 |
| 13 | 1200 | 75.64 |
| 14 | 1300 | 73.83 |
| 15 | 1400 | 73.13 |
| 16 | 1500 | 75.50 |
| 17 | 1600 | 76.15 |
| 18 | 1700 | 73.42 |
| 19 | 1800 | 73.37 |
| 20 | 1900 | 76.38 |
| 21 | 2000 | 73.53 |
| 22 | 2100 | 74.38 |
| 23 | 2200 | 72.70 |
| 24 | 2300 | 73.11 |
| 25 | 2400 | 74.61 |
| 26 | 2500 | 74.05 |
| 27 | 2600 | 79.58 |
| 28 | 2700 | 76.30 |
| 29 | 2800 | 79.67 |
| 30 | 2900 | 78.16 |
| 31 | 3000 | 76.77 |
| 32 | 3100 | 81.41 |
| 33 | 3200 | 77.72 |
| 34 | 3300 | 76.68 |
| 35 | 3400 | 74.73 |
| 36 | 3500 | 72.84 |
| 37 | 3600 | 74.49 |
| 38 | 3700 | 73.15 |
| 39 | 3800 | 72.61 |
| 40 | 3900 | 73.49 |
| 41 | 4000 | 87.08 |
| 42 | 4100 | 79.66 |
| 43 | 4200 | 75.63 |
| 44 | 4300 | 78.24 |
| 45 | 4400 | 85.77 |
| 46 | 4500 | 79.69 |
| 47 | 4600 | 75.14 |
| 48 | 4700 | 73.31 |
| 49 | 4800 | 77.97 |
| 50 | 4900 | 74.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 Amsterdam (52.37403, 4.88969) and Ashburn (39.04372, -77.48749). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 6,223.2 km |
| Vacuum RTT floor | 41.52 ms |
| Standard fiber RTT floor () | 60.94 ms |
| Low-latency fiber material floor | 60.7 ms |
| Engineering floor (5% path allowance) | 64 ms |
| Research 1.33× mapped-fiber reference | 81.05 ms |
| Estimated unamplified path loss | 1306.9 dB |
| Transparent optical spans / inline amplifiers | 82 / 81 |
| Published RTT inflation over fiber floor | 1.24× |
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-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 71.94 ms |
| Average RTT | 75.7 ms |
| Maximum RTT | 87.08 ms |
| Standard deviation | 3.2 ms |
| Stdev / average | 4.2% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 75.7 ms
- Minimum
- 75.2 ms
- Maximum
- 76.6 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Amsterdam (AMS)
- Destination PoP: Ashburn (IAD)
- Region overview: Europe → North America
- Corridor overview: Europe to North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Ashburn to Amsterdam latency and RTT — 75.7 ms
Fastest routes departing Amsterdam (AMS)
- Amsterdam to London latency and RTT — 5.1 ms
- Amsterdam to Frankfurt latency and RTT — 5.9 ms
- Amsterdam to Paris latency and RTT — 7 ms
- Amsterdam to Berlin latency and RTT — 7.2 ms
- Amsterdam to Marseille latency and RTT — 19.7 ms
Fastest routes arriving at Ashburn (IAD)
- New York to Ashburn latency and RTT — 6 ms
- Miami to Ashburn latency and RTT — 27.3 ms
- Los Angeles to Ashburn latency and RTT — 59.9 ms
- Seattle to Ashburn latency and RTT — 62 ms
- London to Ashburn latency and RTT — 71.3 ms
Same corridor (Europe → North America)
- London to New York latency and RTT — 63.5 ms
- Amsterdam to New York latency and RTT — 68.2 ms
- Paris to New York latency and RTT — 68.6 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/ams-iad.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Ashburn round 2026-08-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.