Moscow, Russia → New York, USA RTT

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

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

From Moscow to New York, the 2026-08-16T04:07:28Z round measured an average ICMP RTT of 107.5 ms, a minimum of 103.9 ms, and a maximum of 121.54 ms. The 3.46 ms standard deviation and 2.69 ms jitter indicate a steady transatlantic path, and all 50 probes returned without loss.

For the 7,531.3 km great-circle distance, the vacuum floor is 50.24 ms and the fiber floor is 73.75 ms. The route runs 1.46 times the fiber floor, or 68.6% fiber efficiency, which leaves less room for distance-based improvement than most long intercontinental paths.

This path ranks 7th of the 19 outbound routes in the set by average latency. Its relative variability of 3.2% is just below the 3.28% median, so the Good-tier latency is paired with consistency typical of the better-performing half of the route group.

The route-specific takeaway is tight but not perfectly flat: the min-to-max range is 17.64 ms, while the average and standard deviation suggest most probes land within a few milliseconds of 107.5 ms. Zero packet loss and a fiber efficiency near 69% make this a well-behaved long-haul result.

Latency Summary

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.

Sample distribution: box = interquartile range (105.4–108.3 ms), median 106.4 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	104.24
2	100	105.83
3	200	109.39
4	300	105.90
5	400	105.67
6	500	121.54
7	600	116.39
8	700	108.41
9	800	107.54
10	900	105.86
11	1000	105.80
12	1100	105.15
13	1200	105.32
14	1300	106.82
15	1400	105.50
16	1500	107.47
17	1600	107.87
18	1700	106.07
19	1800	106.55
20	1900	105.21
21	2000	106.54
22	2100	106.90
23	2200	105.36
24	2300	104.27
25	2400	105.90
26	2500	109.26
27	2600	105.81
28	2700	104.63
29	2800	105.39
30	2900	104.24
31	3000	103.90
32	3100	104.18
33	3200	114.46
34	3300	107.45
35	3400	106.21
36	3500	116.33
37	3600	109.18
38	3700	107.30
39	3800	107.25
40	3900	105.13
41	4000	107.75
42	4100	110.34
43	4200	112.72
44	4300	109.55
45	4400	105.94
46	4500	104.62
47	4600	107.59
48	4700	109.94
49	4800	108.69
50	4900	105.64

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.

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Moscow (55.75204, 37.61781) and New York City (40.71427, -74.00597). It does not disclose either facility address.

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:

Route Context

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

Related City-Pair Routes

Reverse direction

• New York to Moscow latency and RTT — 107 ms

Fastest routes departing Moscow (MOW)

• Moscow to Berlin latency and RTT — 27.5 ms
• Moscow to Frankfurt latency and RTT — 35.9 ms
• Moscow to Amsterdam latency and RTT — 37.6 ms
• Moscow to London latency and RTT — 42.4 ms
• Moscow to Paris latency and RTT — 44 ms

Fastest routes arriving at New York (NYC)

• Ashburn to New York latency and RTT — 6 ms
• Miami to New York latency and RTT — 33.3 ms
• Los Angeles to New York latency and RTT — 57.9 ms
• Seattle to New York latency and RTT — 59.5 ms
• London to New York latency and RTT — 63.8 ms

Same corridor (Europe → North America)

• Amsterdam to New York latency and RTT — 68.6 ms
• Paris to New York latency and RTT — 68.9 ms
• London to Ashburn latency and RTT — 71 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-nyc.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → New York 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.