# Moscow, Russia → Seattle, USA RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Seattle, USA (SEA)**

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

For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to Seattle averaged 164.8 ms across 50 samples, with a minimum of 155.86 ms and a maximum of 193.38 ms. No packets were lost, so the route’s stability is defined by timing rather than reachability.

The great-circle distance of about 8,397 km gives a fiber-floor estimate near 82 ms, meaning the observed average is roughly two times the floor and fiber efficiency is 49.9 percent. A standard deviation of 7.9 ms and jitter of 6.37 ms keep the path fairly steady despite the headroom above the floor.

This route ranked 14th among 19 Moscow outbound paths in this round; the median variability across the Moscow outbound set was 3.28 percent of average latency. At 4.8 percent of average latency, this route’s own variability sits above that median, and the max sample sits 28.6 ms above the average, a tail worth watching.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **164.8 ms**                                                 |
| Jitter               | **6.37 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **82.23 ms**                                                 |
| Fiber Efficiency     | **49.9%**                                                    |
| Latency Tier         | Fair                                                         |
| 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 [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **8,396.9 km** |
| Vacuum RTT floor                              | **56.02 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **82.23 ms**   |
| Low-latency fiber material floor              | **81.9 ms**    |
| Engineering floor (5% path allowance)         | **86.35 ms**   |
| Research 1.33× mapped-fiber reference         | **109.36 ms**  |
| Estimated unamplified path loss               | **1763.3 dB**  |
| Transparent optical spans / inline amplifiers | **111 / 110**  |
| Published RTT inflation over fiber floor      | **2×**         |

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        | **155.86 ms** |
| Average RTT        | **164.8 ms**  |
| Maximum RTT        | **193.38 ms** |
| Standard deviation | **7.9 ms**    |
| Stdev / average    | **4.8%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* 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**

* [Seattle to Moscow latency and RTT](/docs/network/latency/pairs/sea-mow-rtt) — 164.6 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 Seattle (SEA)**

* [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms
* [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms
* [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 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-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Seattle 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-sea-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.