Berlin, Germany to Seattle, USA ICMP round-trip time (RTT) measurements: average latency, jitter, packet loss, and route efficiency for network diagnostics.

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

Measurement round: 2026-08-16T04:07:28Z.

During the measurement round 2026-08-16T04:07:28Z, 50 ICMP echo probes from Berlin to Seattle produced an average RTT of 139.7 ms, with a minimum of 135.21 ms, a maximum of 156.43 ms, and no packet loss. Jitter of 3.54 ms and a standard deviation of 4.65 ms place the route in the good latency tier.

The 139.7 ms average is 1.75 times the 79.73 ms fiber floor for an 8,142.2 km geodesic distance, yielding 57.1 percent fiber efficiency. The distribution is wider in absolute terms, yet the route remains loss-free across all probes.

Among the 19 outbound routes in this cycle, Berlin-Seattle is ranked 10th, and its standard deviation is about 3.3 percent of the average RTT, essentially matching the 3.28 percent median across the route set. For a Pacific Northwest interconnection hub, this consistency gives network teams a reliable RTT baseline toward Seattle.

Latency Summary

Metric	Value
RTT	139.7 ms
Jitter	3.54 ms
Packet Loss	0%
Standard Fiber Floor	79.73 ms
Fiber Efficiency	57.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: BER → SEA

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 139.7 ± 0.66 ms (SE)

Sample distribution: box = interquartile range (136.6–141.0 ms), median 138.0 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	135.21
2	100	136.00
3	200	148.76
4	300	141.30
5	400	137.48
6	500	136.16
7	600	136.88
8	700	144.14
9	800	139.10
10	900	137.66
11	1000	136.42
12	1100	135.87
13	1200	135.61
14	1300	136.42
15	1400	143.75
16	1500	138.29
17	1600	153.90
18	1700	156.43
19	1800	146.68
20	1900	139.19
21	2000	137.65
22	2100	137.41
23	2200	136.38
24	2300	136.76
25	2400	136.13
26	2500	135.52
27	2600	137.42
28	2700	146.15
29	2800	141.09
30	2900	139.05
31	3000	136.50
32	3100	135.63
33	3200	135.70
34	3300	139.10
35	3400	138.03
36	3500	137.52
37	3600	138.44
38	3700	143.05
39	3800	139.64
40	3900	137.13
41	4000	140.22
42	4100	137.64
43	4200	150.42
44	4300	140.95
45	4400	139.95
46	4500	140.96
47	4600	137.57
48	4700	140.96
49	4800	138.79
50	4900	137.99

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.75×

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	135.21 ms
Average RTT	139.7 ms
Maximum RTT	156.43 ms
Standard deviation	4.65 ms
Stdev / average	3.3%

RTT trend

Estimated route stability across the selected time window.

Average: 139.8 ms
Minimum: 138.5 ms
Maximum: 141.2 ms
Average loss: 0.02%

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 — 140.9 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 London latency and RTT — 15.2 ms
Berlin to Paris latency and RTT — 15.6 ms
Berlin to Marseille latency and RTT — 20.2 ms

Fastest routes arriving at Seattle (SEA)

Los Angeles to Seattle latency and RTT — 26.9 ms
New York to Seattle latency and RTT — 58.7 ms
Ashburn to Seattle latency and RTT — 62.3 ms
Miami to Seattle latency and RTT — 81.9 ms
Tokyo to Seattle latency and RTT — 84.8 ms

Same corridor (Europe → North America)

London to New York latency and RTT — 63.8 ms
Amsterdam to New York latency and RTT — 68.6 ms
Paris to New York latency and RTT — 68.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/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-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.

Berlin, Germany → Seattle, USA RTT