Seattle, USA to Amsterdam, Netherlands: ICMP echo RTT statistics, jitter, packet loss, fiber efficiency from the 2026-08-15 measurement round.

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

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

In the 2026-08-15T04:03:13Z round, ICMP echo RTT from Seattle to Amsterdam averaged 129.6 ms over 50 samples, with a minimum of 124.65 ms and a maximum of 139.62 ms. The route reported zero packet loss and 3.34 ms jitter, placing it in the Good latency tier.

It ranked 9th among the 19 outbound routes measured in the same round, a middle position. Variability of about 2.9% of the average RTT was slightly lower than the 3.08% median variability across the route set, indicating a steady trace without excessive fluctuation.

The average sits 1.69 times above the theoretical fiber floor for the 7,849 km great-circle distance, equivalent to 59.3% fiber efficiency. The 69% gap between the observed RTT and the theoretical minimum is moderate for a route spanning this geography, and the stable jitter and zero loss show the route holding its Good-tier latency consistently.

Latency Summary

Metric	Value
RTT	129.6 ms
Jitter	3.34 ms
Packet Loss	0%
Standard Fiber Floor	76.86 ms
Fiber Efficiency	59.3%
Latency Tier	Good
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: SEA → AMS

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

Sample distribution: box = interquartile range (126.8–131.0 ms), median 129.1 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	129.04
2	100	130.41
3	200	129.38
4	300	130.93
5	400	139.62
6	500	132.17
7	600	131.07
8	700	128.95
9	800	127.39
10	900	128.15
11	1000	126.87
12	1100	125.08
13	1200	132.76
14	1300	133.61
15	1400	129.24
16	1500	127.42
17	1600	128.35
18	1700	126.99
19	1800	124.91
20	1900	124.65
21	2000	127.37
22	2100	125.30
23	2200	130.28
24	2300	138.80
25	2400	136.33
26	2500	129.43
27	2600	138.09
28	2700	129.06
29	2800	126.27
30	2900	125.45
31	3000	129.17
32	3100	129.34
33	3200	131.37
34	3300	128.69
35	3400	125.81
36	3500	125.19
37	3600	137.30
38	3700	129.34
39	3800	128.70
40	3900	131.89
41	4000	130.86
42	4100	137.81
43	4200	130.42
44	4300	131.18
45	4400	126.34
46	4500	129.61
47	4600	126.84
48	4700	124.86
49	4800	125.53
50	4900	126.38

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 Seattle (47.60621, -122.33207) and Amsterdam (52.37403, 4.88969). 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	124.65 ms
Average RTT	129.6 ms
Maximum RTT	139.62 ms
Standard deviation	3.82 ms
Stdev / average	2.9%

RTT trend

Estimated route stability across the selected time window.

Average: 129.4 ms
Minimum: 128.2 ms
Maximum: 130.7 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Amsterdam to Seattle latency and RTT — 130.1 ms

Fastest routes departing Seattle (SEA)

Seattle to Los Angeles latency and RTT — 26.6 ms
Seattle to New York latency and RTT — 59 ms
Seattle to Ashburn latency and RTT — 62 ms
Seattle to Miami latency and RTT — 81.1 ms
Seattle to Tokyo latency and RTT — 84.8 ms

Fastest routes arriving at Amsterdam (AMS)

London to Amsterdam latency and RTT — 5.1 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 — 19.6 ms

Same corridor (North America → Europe)

New York to London latency and RTT — 64.3 ms
New York to Paris latency and RTT — 68.4 ms
New York to Amsterdam latency and RTT — 68.5 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/sea-ams.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Amsterdam 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.

Seattle, USA → Amsterdam, Netherlands RTT