Moscow to New York ping and RTT: 105.2 ms, 1.49 ms jitter, 73.75 ms fiber floor, and 70.1% efficiency across AS203314. Updated 2026-08-09.

🇷🇺 This page compares the published ping and round-trip time (RTT) from Moscow (MOW) to 🇺🇸 New York (NYC) with vacuum and optical-fiber physical limits.

As of August 9, 2026, the Moscow → New York route on Hats Network averages 105.2 ms RTT across a 50-sample daily ICMP echo measurement round (source: RETN), 1.43× the theoretical fiber-floor limit of 73.75 ms.

Among the 19 measured routes departing Moscow, this route ranks 7th fastest by average RTT.

With a stdev-to-average ratio of 1.6%, this route is more stable than the network median of 3.4%. Across the round, per-probe RTT ranged from 103.21 ms to 110.77 ms with a standard deviation of 1.67 ms.

Latency Summary

Metric	Value
RTT	105.2 ms
Jitter	1.49 ms
Packet Loss	0%
Standard Fiber Floor	73.75 ms
Fiber Efficiency	70.1%
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 → NYC

50 ICMP echo samples at 100 ms intervals · round 2026-08-09 · avg 105.2 ± 0.24 ms (SE)

Sample distribution: box = interquartile range (104.0–106.2 ms), median 104.7 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.00
2	100	104.95
3	200	107.09
4	300	108.07
5	400	106.19
6	500	104.19
7	600	104.94
8	700	105.29
9	800	107.33
10	900	104.43
11	1000	104.87
12	1100	103.71
13	1200	103.34
14	1300	106.59
15	1400	110.77
16	1500	106.65
17	1600	104.68
18	1700	103.45
19	1800	104.33
20	1900	103.33
21	2000	103.96
22	2100	103.57
23	2200	107.61
24	2300	106.02
25	2400	104.24
26	2500	103.21
27	2600	104.35
28	2700	104.15
29	2800	103.38
30	2900	103.34
31	3000	103.53
32	3100	106.22
33	3200	106.24
34	3300	106.55
35	3400	105.26
36	3500	107.04
37	3600	104.18
38	3700	104.15
39	3800	108.58
40	3900	105.24
41	4000	104.23
42	4100	104.18
43	4200	108.09
44	4300	107.52
45	4400	105.37
46	4500	104.68
47	4600	104.21
48	4700	103.85
49	4800	103.29
50	4900	105.56

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 New York City (40.71427, -74.00597). 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.43×

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-09) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	103.21 ms
Average RTT	105.2 ms
Maximum RTT	110.77 ms
Standard deviation	1.67 ms
Stdev / average	1.6%

RTT trend

Estimated route stability across the selected time window.

Average: 105.3 ms
Minimum: 104.4 ms
Maximum: 106.2 ms
Average loss: 0.03%

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

Reverse direction

New York to Moscow latency and RTT — 105.1 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 28.6 ms
Moscow to Frankfurt latency and RTT — 35.4 ms
Moscow to Amsterdam latency and RTT — 37.9 ms
Moscow to London latency and RTT — 43 ms
Moscow to Paris latency and RTT — 44.2 ms

Fastest routes arriving at New York (NYC)

Ashburn to New York latency and RTT — 6.1 ms
Miami to New York latency and RTT — 33.5 ms
Seattle to New York latency and RTT — 58.7 ms
Los Angeles to New York latency and RTT — 59 ms
London to New York latency and RTT — 64 ms

Same corridor (Europe → North America)

Amsterdam to New York latency and RTT — 69.3 ms
Paris to New York latency and RTT — 69.3 ms
London to Ashburn latency and RTT — 70.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-nyc.pings.{csv,json,yaml}. When citing, include the route, the measurement round date, and the dataset version — for example: "Hats Network latency dataset, Moscow → New York round 2026-08-09, CC BY 4.0".

Data auto-generated on August 9, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Moscow to New York Latency, Ping & RTT | AS203314