# 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

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **107.5 ms**                                                 |
| Jitter               | **2.69 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **73.75 ms**                                                 |
| Fiber Efficiency     | **68.6%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [Europe](/docs/network/latency/regions/europe)               |
| Destination Region   | [North America](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [New York City](https://www.geonames.org/5128581) (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.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](/docs/network/latency/theoretical-fiber-latency).

## 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        | **103.9 ms**  |
| Average RTT        | **107.5 ms**  |
| Maximum RTT        | **121.54 ms** |
| Standard deviation | **3.46 ms**   |
| Stdev / average    | **3.2%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america)
* Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [New York to Moscow latency and RTT](/docs/network/latency/pairs/nyc-mow-rtt) — 107 ms

**Fastest routes departing Moscow (MOW)**

* [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms
* [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms
* [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms
* [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms

**Fastest routes arriving at New York (NYC)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms

**Same corridor (Europe → North America)**

* [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms
* [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 ms
* [London to Ashburn latency and RTT](/docs/network/latency/pairs/lon-iad-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](/opendata/latency/). 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](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-nyc-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.