Moscow to Ashburn RTT measurement: ICMP echo latency, jitter, packet loss, and route efficiency between Russia and USA in round 2026-08-15T04:03:13Z.

🇷🇺 Moscow, Russia (MOW) → 🇺🇸 Ashburn, USA (IAD)

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

Measurement round 2026-08-15T04:03:13Z for Moscow-to-Ashburn averaged 112.3 ms of ICMP echo RTT, with a minimum of 110.01 ms and a maximum of 120.92 ms across 50 samples. The 2.01 ms standard deviation and 1.89 ms jitter put the transatlantic route in the Good latency tier, and packet loss was 0%.

Against the 76.88 ms straight-line fiber floor, the observed average is 1.46 times higher, yielding 68.5% direct-fiber efficiency. The route ranked 8th among the 19 outbound paths in this round, while its own variability of about 1.8% was well below the round-wide median variability of 3.08%.

Despite the nearly 7,900 km geographic span to the US East Coast corridor, the sub-2 ms jitter and zero loss indicate a steady path; this round can serve as a clean baseline for Moscow-to-Ashburn RTT expectations.

Latency Summary

Metric	Value
RTT	112.3 ms
Jitter	1.89 ms
Packet Loss	0%
Standard Fiber Floor	76.88 ms
Fiber Efficiency	68.5%
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: MOW → IAD

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

Sample distribution: box = interquartile range (110.9–113.1 ms), median 111.8 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	113.90
2	100	116.14
3	200	111.90
4	300	110.94
5	400	112.88
6	500	112.25
7	600	111.85
8	700	112.41
9	800	110.62
10	900	111.35
11	1000	110.82
12	1100	112.13
13	1200	110.56
14	1300	111.95
15	1400	110.75
16	1500	115.54
17	1600	112.25
18	1700	111.44
19	1800	114.46
20	1900	111.32
21	2000	112.21
22	2100	111.00
23	2200	113.20
24	2300	114.53
25	2400	112.12
26	2500	111.41
27	2600	111.44
28	2700	115.98
29	2800	120.92
30	2900	113.45
31	3000	110.93
32	3100	110.01
33	3200	113.14
34	3300	112.57
35	3400	110.97
36	3500	110.69
37	3600	111.70
38	3700	110.30
39	3800	111.68
40	3900	114.44
41	4000	111.19
42	4100	110.19
43	4200	111.40
44	4300	110.29
45	4400	112.10
46	4500	110.61
47	4600	110.90
48	4700	110.29
49	4800	115.46
50	4900	114.42

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 Ashburn (39.04372, -77.48749). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	7,850.6 km
Vacuum RTT floor	52.37 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	76.88 ms
Low-latency fiber material floor	76.57 ms
Engineering floor (5% path allowance)	80.73 ms
Research 1.33× mapped-fiber reference	102.25 ms
Estimated unamplified path loss	1648.6 dB
Transparent optical spans / inline amplifiers	104 / 103
Published RTT inflation over fiber floor	1.46×

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	110.01 ms
Average RTT	112.3 ms
Maximum RTT	120.92 ms
Standard deviation	2.01 ms
Stdev / average	1.8%

RTT trend

Estimated route stability across the selected time window.

Average: 112.5 ms
Minimum: 111.1 ms
Maximum: 113.6 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Ashburn to Moscow latency and RTT — 113 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 Ashburn (IAD)

New York to Ashburn latency and RTT — 6 ms
Miami to Ashburn latency and RTT — 27.3 ms
Los Angeles to Ashburn latency and RTT — 59.9 ms
Seattle to Ashburn latency and RTT — 62 ms
London to Ashburn latency and RTT — 71.3 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-iad.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Ashburn 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 → Ashburn, USA RTT