See New York, USA to Moscow, Russia ICMP RTT metrics: 107 ms average, 101.46 ms minimum, 0% packet loss, jitter 3.73 ms, plus efficiency context.

🇺🇸 New York, USA (NYC) → 🇷🇺 Moscow, Russia (MOW)

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

On the 2026-08-16T04:07:28Z round, ICMP echo RTT from New York, USA to Moscow, Russia averaged 107 ms, with a 101.46 ms minimum, 119.28 ms maximum, 4.26 ms standard deviation, and 3.73 ms jitter. All 50 samples returned without packet loss.

Against the 50.24 ms vacuum floor and 73.75 ms straight-line fiber floor for the 7,531.3 km separation, the observed average is 1.45 times the fiber floor, or 68.9% fiber efficiency. The extra time reflects the practical distance of a transatlantic-and-continental route, while the stable minimum and zero loss keep this path in the Good latency tier.

This link ranked 12th among the round's 19 outbound routes. Its standard deviation is about 3.98% of the average, slightly above the 3.28% median variability for that route set. For teams treating Moscow as a gateway toward Asia-Pacific, this 107 ms RTT provides a useful eastward baseline from the US East Coast.

Latency Summary

Metric	Value
RTT	107 ms
Jitter	3.73 ms
Packet Loss	0%
Standard Fiber Floor	73.75 ms
Fiber Efficiency	68.9%
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: NYC → MOW

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

Sample distribution: box = interquartile range (103.9–108.8 ms), median 105.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 (73.8 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	101.53
2	100	105.81
3	200	103.15
4	300	102.31
5	400	107.85
6	500	106.09
7	600	104.59
8	700	103.95
9	800	103.38
10	900	103.86
11	1000	110.94
12	1100	113.89
13	1200	107.27
14	1300	119.28
15	1400	107.88
16	1500	115.77
17	1600	107.62
18	1700	112.98
19	1800	106.98
20	1900	103.47
21	2000	101.88
22	2100	101.46
23	2200	106.18
24	2300	104.24
25	2400	107.88
26	2500	113.94
27	2600	110.08
28	2700	114.20
29	2800	108.23
30	2900	104.94
31	3000	105.64
32	3100	105.98
33	3200	103.90
34	3300	101.95
35	3400	105.04
36	3500	103.48
37	3600	103.95
38	3700	113.92
39	3800	111.03
40	3900	105.68
41	4000	105.87
42	4100	116.13
43	4200	109.00
44	4300	109.21
45	4400	108.18
46	4500	104.21
47	4600	103.36
48	4700	101.97
49	4800	105.48
50	4900	104.39

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 New York City (40.71427, -74.00597) and Moscow (55.75204, 37.61781). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	7,531.3 km
Vacuum RTT floor	50.24 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	73.75 ms
Low-latency fiber material floor	73.46 ms
Engineering floor (5% path allowance)	77.45 ms
Research 1.33× mapped-fiber reference	98.09 ms
Estimated unamplified path loss	1581.6 dB
Transparent optical spans / inline amplifiers	99 / 98
Published RTT inflation over fiber floor	1.45×

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	101.46 ms
Average RTT	107 ms
Maximum RTT	119.28 ms
Standard deviation	4.26 ms
Stdev / average	4.0%

RTT trend

Estimated route stability across the selected time window.

Average: 107.1 ms
Minimum: 105.8 ms
Maximum: 107.9 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Moscow to New York latency and RTT — 107.5 ms

Fastest routes departing New York (NYC)

New York to Ashburn latency and RTT — 6 ms
New York to Miami latency and RTT — 32.9 ms
New York to Seattle latency and RTT — 58.7 ms
New York to Los Angeles latency and RTT — 58.9 ms
New York to London latency and RTT — 63.5 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 Amsterdam latency and RTT — 68.7 ms
New York to Paris latency and RTT — 68.9 ms
Ashburn to London latency and RTT — 70.3 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/nyc-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, New York → 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.

New York, USA → Moscow, Russia RTT