# Moscow, Russia → Ashburn, USA RTT

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

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

In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Moscow to Ashburn averaged 113.9 ms over 50 samples, with a minimum of 107.82 ms and a maximum of 129.74 ms. The route had zero packet loss, though jitter of 4.1 ms and a 5.37 ms standard deviation place it in the good latency tier rather than excellent.

For a geodesic separation of 7,850.6 km, the average is 1.48 times the 76.88 ms theoretical fiber floor, a 67.5% efficiency ratio. Among the 19 Moscow-origin routes in this round, this path ranks eighth by average RTT; its spread-to-average ratio of about 4.7% is above the 3.28% median for the route set.

The main takeaway is that the long transatlantic path is efficiently routed in terms of distance versus RTT, but the sample tail is wider: the maximum ran 15.84 ms above the average, about 13.9% higher. Loss-free operation keeps the profile clean despite the wider spread separating this route from the excellent tier.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **113.9 ms**                                                 |
| Jitter               | **4.1 ms**                                                   |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **76.88 ms**                                                 |
| Fiber Efficiency     | **67.5%**                                                    |
| 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 [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749). 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.48×**      |

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        | **107.82 ms** |
| Average RTT        | **113.9 ms**  |
| Maximum RTT        | **129.74 ms** |
| Standard deviation | **5.37 ms**   |
| Stdev / average    | **4.7%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn)
* 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**

* [Ashburn to Moscow latency and RTT](/docs/network/latency/pairs/iad-mow-rtt) — 112.8 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 Ashburn (IAD)**

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

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

* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms
* [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

## 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-iad.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Ashburn 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-iad-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.