Berlin to Seattle ICMP RTT page: average and minimum latency, jitter, packet loss, and route efficiency measurements between Germany and the USA.

🇩🇪 Berlin, Germany (BER) → 🇺🇸 Seattle, USA (SEA)

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

The 2026-08-15T04:03:13Z measurement for Berlin-to-Seattle, Germany-to-USA, returned a 137.7 ms average RTT over 50 ICMP echo replies, with a minimum of 130.83 ms and a maximum of 155.41 ms. The route experienced zero packet loss and 4.74 ms jitter, matching the Good latency tier over 8,142.2 km.

This path is ranked 10th in the 19-route outbound set, putting it near the midpoint. Its standard deviation of 6.15 ms is 4.5 percent of the average RTT, a bit wider than the group's typical 3.08 percent spread relative to average latency, so the stability is acceptable but not as tight as some other routes in the set.

The observed RTT is 1.73 times the 79.73 ms fiber floor, for a fiber efficiency of 57.9 percent, and the additional 57.97 ms above that floor shows room for a less direct path. Seattle is a primary Pacific Northwest interconnection hub and a landing point for trans-Pacific cables toward Japan and East Asia, so zero-loss, Good-tier latency is a relevant baseline for reaching that hub from Europe.

Latency Summary

Metric	Value
RTT	137.7 ms
Jitter	4.74 ms
Packet Loss	0%
Standard Fiber Floor	79.73 ms
Fiber Efficiency	57.9%
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: BER → SEA

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

Sample distribution: box = interquartile range (133.4–139.1 ms), median 136.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 (79.7 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	133.37
2	100	133.80
3	200	139.83
4	300	137.61
5	400	132.18
6	500	130.83
7	600	133.36
8	700	130.91
9	800	135.60
10	900	137.05
11	1000	132.35
12	1100	139.15
13	1200	152.11
14	1300	150.43
15	1400	139.73
16	1500	143.32
17	1600	140.26
18	1700	152.02
19	1800	137.98
20	1900	137.56
21	2000	139.64
22	2100	139.05
23	2200	135.68
24	2300	133.23
25	2400	131.12
26	2500	135.50
27	2600	134.08
28	2700	136.30
29	2800	132.23
30	2900	132.61
31	3000	131.66
32	3100	135.87
33	3200	133.98
34	3300	134.84
35	3400	152.18
36	3500	142.99
37	3600	138.89
38	3700	132.62
39	3800	137.87
40	3900	134.20
41	4000	133.93
42	4100	132.39
43	4200	138.53
44	4300	155.41
45	4400	151.07
46	4500	137.21
47	4600	133.40
48	4700	137.35
49	4800	133.62
50	4900	138.10

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 Berlin (52.52437, 13.41053) and Seattle (47.60621, -122.33207). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,142.2 km
Vacuum RTT floor	54.32 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	79.73 ms
Low-latency fiber material floor	79.41 ms
Engineering floor (5% path allowance)	83.73 ms
Research 1.33× mapped-fiber reference	106.05 ms
Estimated unamplified path loss	1709.9 dB
Transparent optical spans / inline amplifiers	107 / 106
Published RTT inflation over fiber floor	1.73×

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	130.83 ms
Average RTT	137.7 ms
Maximum RTT	155.41 ms
Standard deviation	6.15 ms
Stdev / average	4.5%

RTT trend

Estimated route stability across the selected time window.

Average: 137.9 ms
Minimum: 136.5 ms
Maximum: 138.8 ms
Average loss: 0.01%

Route Context

Departure PoP: Berlin (BER)
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 Berlin latency and RTT — 138.5 ms

Fastest routes departing Berlin (BER)

Berlin to Frankfurt latency and RTT — 6.1 ms
Berlin to Amsterdam latency and RTT — 7.2 ms
Berlin to Paris latency and RTT — 14.2 ms
Berlin to London latency and RTT — 15.9 ms
Berlin to Marseille latency and RTT — 20.5 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/ber-sea.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → 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.

Berlin, Germany → Seattle, USA RTT