ICMP echo RTT measurements from Moscow, Russia to Seattle, USA: average latency, jitter, packet loss and route efficiency for this trans-Pacific link.

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

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

During the 2026-08-15T04:03:13Z measurement round, the 50 ICMP echo samples from Moscow to Seattle averaged 165.2 ms RTT, with a minimum of 158.26 ms and a maximum of 182.68 ms. No packets were lost.

That average is roughly 2.01 times the theoretical fiber-floor transit time over the 8,396.9 km great-circle distance, so the route realizes about 49.8% direct-line fiber efficiency. The 5.33 ms standard deviation and 5.69 ms jitter indicate a consistent path, and the Fair latency tier reflects the high absolute RTT.

This route ranked 14th among the 19 outbound paths from Moscow in this round, placing it in the slower half of the set. Its relative variability of about 3.2% is close to the network's median relative variability of 3.08%, so the main limitation is total transit time rather than stability.

Latency Summary

Metric	Value
RTT	165.2 ms
Jitter	5.69 ms
Packet Loss	0%
Standard Fiber Floor	82.23 ms
Fiber Efficiency	49.8%
Latency Tier	Fair
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: MOW → SEA

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

Sample distribution: box = interquartile range (161.4–168.4 ms), median 164.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	158.26
2	100	160.65
3	200	158.64
4	300	166.68
5	400	161.41
6	500	165.75
7	600	161.44
8	700	160.74
9	800	158.72
10	900	177.62
11	1000	169.54
12	1100	161.61
13	1200	159.57
14	1300	174.03
15	1400	164.14
16	1500	162.18
17	1600	182.68
18	1700	169.15
19	1800	170.59
20	1900	164.78
21	2000	172.28
22	2100	163.83
23	2200	160.10
24	2300	160.92
25	2400	163.07
26	2500	167.79
27	2600	161.17
28	2700	164.70
29	2800	162.48
30	2900	165.08
31	3000	161.54
32	3100	158.84
33	3200	159.96
34	3300	158.44
35	3400	168.61
36	3500	164.02
37	3600	172.45
38	3700	162.87
39	3800	164.27
40	3900	164.14
41	4000	162.68
42	4100	174.48
43	4200	165.43
44	4300	162.52
45	4400	168.76
46	4500	164.99
47	4600	173.24
48	4700	166.30
49	4800	164.68
50	4900	172.18

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 Moscow (55.75204, 37.61781) and Seattle (47.60621, -122.33207). 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.01×

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	158.26 ms
Average RTT	165.2 ms
Maximum RTT	182.68 ms
Standard deviation	5.33 ms
Stdev / average	3.2%

RTT trend

Estimated route stability across the selected time window.

Average: 164.8 ms
Minimum: 163.4 ms
Maximum: 165.9 ms
Average loss: 0.01%

Route Context

Departure PoP: Moscow (MOW)
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 Moscow latency and RTT — 164.6 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27 ms
Moscow to Frankfurt latency and RTT — 35 ms
Moscow to Amsterdam latency and RTT — 39.3 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 43.9 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/mow-sea.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → 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.

Moscow, Russia → Seattle, USA RTT