ICMP echo RTT from Seattle, USA to Moscow, Russia: average, minimum, maximum, jitter and packet loss for 50 probes in a single measurement round.

🇺🇸 Seattle, USA (SEA) → 🇷🇺 Moscow, Russia (MOW)

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

In the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Seattle, USA to Moscow, Russia produced an average RTT of 164.6 ms, with a minimum of 158.38 ms and a maximum of 192.7 ms. Zero packet loss and 5 ms jitter keep the route within the Fair latency tier.

This route was ranked 17th among the 19 Seattle outbound routes measured in the same round. Its standard deviation of 7.23 ms is about 4.4% of the average RTT, higher than the 3.28% median variability for the route set.

At a geodesic distance of 8,396.9 km, the theoretical fiber floor is 82.23 ms, so the observed RTT is twice that floor and yields 50% fiber efficiency. The lower efficiency and Fair tier suggest this route has less latency headroom than its geographic distance alone might imply.

Latency Summary

Metric	Value
RTT	164.6 ms
Jitter	5 ms
Packet Loss	0%
Standard Fiber Floor	82.23 ms
Fiber Efficiency	50%
Latency Tier	Fair
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 → MOW

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

Sample distribution: box = interquartile range (159.7–166.0 ms), median 162.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 (82.2 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	164.27
2	100	163.45
3	200	159.85
4	300	158.99
5	400	158.77
6	500	160.23
7	600	161.93
8	700	162.18
9	800	158.99
10	900	158.40
11	1000	161.14
12	1100	159.31
13	1200	170.38
14	1300	164.58
15	1400	175.29
16	1500	186.12
17	1600	168.09
18	1700	168.08
19	1800	166.18
20	1900	160.52
21	2000	158.38
22	2100	159.22
23	2200	163.90
24	2300	160.03
25	2400	160.20
26	2500	164.49
27	2600	161.58
28	2700	162.49
29	2800	161.52
30	2900	158.89
31	3000	164.50
32	3100	162.33
33	3200	162.22
34	3300	178.12
35	3400	165.24
36	3500	171.07
37	3600	192.70
38	3700	172.55
39	3800	169.56
40	3900	161.64
41	4000	159.52
42	4100	159.20
43	4200	159.71
44	4300	161.52
45	4400	169.56
46	4500	180.18
47	4600	165.30
48	4700	160.06
49	4800	158.89
50	4900	158.68

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 Moscow (55.75204, 37.61781). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,396.9 km
Vacuum RTT floor	56.02 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	82.23 ms
Low-latency fiber material floor	81.9 ms
Engineering floor (5% path allowance)	86.35 ms
Research 1.33× mapped-fiber reference	109.36 ms
Estimated unamplified path loss	1763.3 dB
Transparent optical spans / inline amplifiers	111 / 110
Published RTT inflation over fiber floor	2×

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	158.38 ms
Average RTT	164.6 ms
Maximum RTT	192.7 ms
Standard deviation	7.23 ms
Stdev / average	4.4%

RTT trend

Estimated route stability across the selected time window.

Average: 164.4 ms
Minimum: 162.7 ms
Maximum: 166.1 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Moscow to Seattle latency and RTT — 164.8 ms

Fastest routes departing Seattle (SEA)

Seattle to Los Angeles latency and RTT — 25.9 ms
Seattle to New York latency and RTT — 59.5 ms
Seattle to Ashburn latency and RTT — 61.5 ms
Seattle to Miami latency and RTT — 81.7 ms
Seattle to Tokyo latency and RTT — 85 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28.6 ms
Frankfurt to Moscow latency and RTT — 34.7 ms
Amsterdam to Moscow latency and RTT — 38.1 ms
London to Moscow latency and RTT — 43.5 ms
Paris to Moscow latency and RTT — 44.7 ms

Same corridor (North America → Europe)

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

Seattle, USA → Moscow, Russia RTT