ICMP round-trip time from Ashburn, USA to Moscow, Russia: 112.8 ms average over 50 samples, zero packet loss, with route efficiency context.

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

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

For the 2026-08-16T04:07:28Z run, ICMP probes from Ashburn to Moscow averaged 112.8 ms across 50 samples, with a minimum of 109.18 ms and a maximum of 122.64 ms. Zero packets were lost, and the 3.63 ms standard deviation held jitter to about 3.16 ms, so the path stayed stable for the full measurement window.

The 7,850.6 km great-circle distance defines a 52.37 ms vacuum-latency floor and a 76.88 ms realistic fiber floor. At 112.8 ms, the observed route runs about 1.47 times the fiber floor, or 68.2% fiber efficiency, meaning the extra delay above an ideal fiber path is moderate rather than extreme for a route spanning this geography.

In this round, the route is ranked 12th by RTT among the 19 outbound paths measured from the same starting point. The median standard-deviation-to-average ratio for outbound paths from this starting point is 3.28%, and with zero loss and 3.16 ms jitter, this Moscow path is consistent enough that the 112.8 ms average can serve as a practical RTT baseline for planning; as with any ICMP measurement, it should not be mistaken for a predictor of end-user application performance.

Latency Summary

Metric	Value
RTT	112.8 ms
Jitter	3.16 ms
Packet Loss	0%
Standard Fiber Floor	76.88 ms
Fiber Efficiency	68.2%
Latency Tier	Good
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: IAD → MOW

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

Sample distribution: box = interquartile range (110.4–113.4 ms), median 111.5 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	112.16
2	100	120.12
3	200	113.29
4	300	111.55
5	400	110.95
6	500	110.00
7	600	109.67
8	700	109.69
9	800	109.18
10	900	109.82
11	1000	109.67
12	1100	109.55
13	1200	110.94
14	1300	110.36
15	1400	112.83
16	1500	122.56
17	1600	122.64
18	1700	113.76
19	1800	122.26
20	1900	113.80
21	2000	110.64
22	2100	116.08
23	2200	111.73
24	2300	110.42
25	2400	109.48
26	2500	118.25
27	2600	113.58
28	2700	112.64
29	2800	111.26
30	2900	112.97
31	3000	120.80
32	3100	113.22
33	3200	111.22
34	3300	109.70
35	3400	109.39
36	3500	119.21
37	3600	113.29
38	3700	110.51
39	3800	111.12
40	3900	110.01
41	4000	113.43
42	4100	111.54
43	4200	112.64
44	4300	110.52
45	4400	114.64
46	4500	111.76
47	4600	109.93
48	4700	111.22
49	4800	113.04
50	4900	110.96

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 Ashburn (39.04372, -77.48749) and Moscow (55.75204, 37.61781). 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.47×

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	109.18 ms
Average RTT	112.8 ms
Maximum RTT	122.64 ms
Standard deviation	3.63 ms
Stdev / average	3.2%

RTT trend

Estimated route stability across the selected time window.

Average: 112.8 ms
Minimum: 111.9 ms
Maximum: 113.8 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Moscow to Ashburn latency and RTT — 113.9 ms

Fastest routes departing Ashburn (IAD)

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

Ashburn, USA → Moscow, Russia RTT