# Ashburn, USA → Moscow, Russia RTT

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

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

For the 2026-08-16T04:07:28Z run, ICMP probes from Ashburn to Moscow averaged 112.8 ms across 50 samples, with a minimum of 109.18 ms and a maximum of 122.64 ms. Zero packets were lost, and the 3.63 ms standard deviation held jitter to about 3.16 ms, so the path stayed stable for the full measurement window.

The 7,850.6 km great-circle distance defines a 52.37 ms vacuum-latency floor and a 76.88 ms realistic fiber floor. At 112.8 ms, the observed route runs about 1.47 times the fiber floor, or 68.2% fiber efficiency, meaning the extra delay above an ideal fiber path is moderate rather than extreme for a route spanning this geography.

In this round, the route is ranked 12th by RTT among the 19 outbound paths measured from the same starting point. The median standard-deviation-to-average ratio for outbound paths from this starting point is 3.28%, and with zero loss and 3.16 ms jitter, this Moscow path is consistent enough that the 112.8 ms average can serve as a practical RTT baseline for planning; as with any ICMP measurement, it should not be mistaken for a predictor of end-user application performance.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **112.8 ms**                                                 |
| Jitter               | **3.16 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **76.88 ms**                                                 |
| Fiber Efficiency     | **68.2%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| Destination Region   | [Europe](/docs/network/latency/regions/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.

## 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 [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). 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.47×**      |

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        | **109.18 ms** |
| Average RTT        | **112.8 ms**  |
| Maximum RTT        | **122.64 ms** |
| Standard deviation | **3.63 ms**   |
| Stdev / average    | **3.2%**      |

## Route Context

* Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn)
* Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [Europe](/docs/network/latency/regions/europe)
* 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**

* [Moscow to Ashburn latency and RTT](/docs/network/latency/pairs/mow-iad-rtt) — 113.9 ms

**Fastest routes departing Ashburn (IAD)**

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

**Fastest routes arriving at Moscow (MOW)**

* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms
* [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms
* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms

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

* [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms
* [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms
* [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-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/iad-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → Moscow 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/iad-mow-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.