ICMP RTT measurements from Amsterdam, Netherlands to Seattle, USA: average latency, jitter, packet loss, and route efficiency for this long-distance route.

🇳🇱 Amsterdam, Netherlands (AMS) → 🇺🇸 Seattle, USA (SEA)

Measurement round: 2026-08-15T04:03:13Z.

In the 2026-08-15T04:03:13Z measurement round, ICMP echo RTT from Amsterdam, Netherlands to Seattle, USA averaged 130.1 ms across 50 samples, with a standard deviation of 1.97 ms and jitter of 1.52 ms. The minimum was 127.89 ms, the maximum was 135.67 ms, and there was no packet loss.

Compared with the 19 outbound routes from Amsterdam, this route ranked 10th by average RTT. Its relative variability was about 1.5% of the average, below the 3.08% median for the same origin's route set, so the path remained consistent throughout the sample window.

The physical reference for this long-distance pair is 7,848.5 km, with an average latency 69% above the theoretical fiber floor and a fiber efficiency of 59.1%. That efficiency gap shows the packet path is considerably longer than a direct great-circle fiber route, even though the measured spread and loss behavior stayed very stable.

Latency Summary

Metric	Value
RTT	130.1 ms
Jitter	1.52 ms
Packet Loss	0%
Standard Fiber Floor	76.86 ms
Fiber Efficiency	59.1%
Latency Tier	Good
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 → SEA

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 130.1 ± 0.28 ms (SE)

Sample distribution: box = interquartile range (128.9–131.1 ms), median 129.3 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 (76.9 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	131.86
2	100	129.04
3	200	128.49
4	300	134.58
5	400	133.30
6	500	129.56
7	600	128.39
8	700	127.92
9	800	131.92
10	900	129.36
11	1000	128.29
12	1100	128.95
13	1200	129.30
14	1300	129.15
15	1400	129.01
16	1500	129.00
17	1600	127.96
18	1700	128.15
19	1800	129.32
20	1900	135.67
21	2000	132.38
22	2100	133.31
23	2200	130.30
24	2300	133.66
25	2400	131.43
26	2500	131.13
27	2600	129.29
28	2700	130.04
29	2800	132.60
30	2900	135.03
31	3000	130.83
32	3100	129.27
33	3200	128.47
34	3300	128.46
35	3400	128.95
36	3500	130.55
37	3600	129.05
38	3700	128.01
39	3800	128.23
40	3900	129.04
41	4000	129.46
42	4100	129.25
43	4200	130.02
44	4300	129.97
45	4400	129.14
46	4500	128.97
47	4600	128.23
48	4700	127.89
49	4800	130.65
50	4900	132.17

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.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Amsterdam (52.37403, 4.88969) and Seattle (47.60621, -122.33207). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	7,848.5 km
Vacuum RTT floor	52.36 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	76.86 ms
Low-latency fiber material floor	76.55 ms
Engineering floor (5% path allowance)	80.71 ms
Research 1.33× mapped-fiber reference	102.22 ms
Estimated unamplified path loss	1648.2 dB
Transparent optical spans / inline amplifiers	104 / 103
Published RTT inflation over fiber floor	1.69×

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	127.89 ms
Average RTT	130.1 ms
Maximum RTT	135.67 ms
Standard deviation	1.97 ms
Stdev / average	1.5%

RTT trend

Estimated route stability across the selected time window.

Average: 130.2 ms
Minimum: 128.8 ms
Maximum: 131.3 ms
Average loss: 0.02%

Route Context

Departure PoP: Amsterdam (AMS)
Destination PoP: Seattle (SEA)
Region overview: Europe → North America
Corridor overview: Europe to North America
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Seattle to Amsterdam latency and RTT — 129.6 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 Seattle (SEA)

Los Angeles to Seattle latency and RTT — 27.5 ms
New York to Seattle latency and RTT — 59 ms
Ashburn to Seattle latency and RTT — 61.3 ms
Miami to Seattle latency and RTT — 82 ms
Tokyo to Seattle latency and RTT — 84.6 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-sea.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → Seattle 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.

Amsterdam, Netherlands → Seattle, USA RTT