# Moscow, Russia → Los Angeles, USA RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇺🇸 **Los Angeles, USA (LAX)**

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

Across the 2026-08-16T04:07:28Z round, Moscow to Los Angeles returned an average ICMP RTT of 177.7 ms, with a minimum of 173.78 ms and a maximum of 191.21 ms. The 3.21 ms standard deviation and 2.25 ms jitter point to a consistent path, and all 50 probes completed without packet loss.

For the 9,793.2 km great-circle distance, the vacuum floor is 65.33 ms and a practical fiber-optic floor is 95.9 ms. At 177.7 ms average, the route sits 1.85 times above the fiber floor—a fiber efficiency of 54%—so the measured latency carries a significant distance penalty relative to the shortest possible optical path.

This path ranks 15th among the 19 outbound routes in the set by average latency. Its relative variability of 1.8% is well below the 3.28% median for the set, meaning the elevated Fair-tier latency is paired with strong stability. If lower RTT is the goal, the most useful avenue is bringing the actual path closer to the fiber floor rather than reducing variance.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **177.7 ms**                                                 |
| Jitter               | **2.25 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **95.9 ms**                                                  |
| Fiber Efficiency     | **54%**                                                      |
| 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 [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,793.2 km** |
| Vacuum RTT floor                              | **65.33 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **95.9 ms**    |
| Low-latency fiber material floor              | **95.52 ms**   |
| Engineering floor (5% path allowance)         | **100.71 ms**  |
| Research 1.33× mapped-fiber reference         | **127.55 ms**  |
| Estimated unamplified path loss               | **2056.6 dB**  |
| Transparent optical spans / inline amplifiers | **129 / 128**  |
| Published RTT inflation over fiber floor      | **1.85×**      |

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        | **173.78 ms** |
| Average RTT        | **177.7 ms**  |
| Maximum RTT        | **191.21 ms** |
| Standard deviation | **3.21 ms**   |
| Stdev / average    | **1.8%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles)
* 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**

* [Los Angeles to Moscow latency and RTT](/docs/network/latency/pairs/lax-mow-rtt) — 177 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 Los Angeles (LAX)**

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