# London, UK → Moscow, Russia RTT

🇬🇧 **London, UK (LON)** → 🇷🇺 **Moscow, Russia (MOW)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo probes from London, UK to Moscow, Russia averaged 43.5 ms over 50 samples, with a minimum of 41.81 ms, a maximum of 48.52 ms, jitter of 1.21 ms, and no packet loss.

With a geodesic distance of 2,508.5 km, the vacuum-floor time is 16.73 ms and the fiber-floor time is 24.56 ms; the observed RTT is 1.77 times the fiber floor, equivalent to 56.5% fiber-floor efficiency. For a route spanning roughly 2,500 km, this is a high-efficiency long-haul path and sits in the Excellent latency tier.

Relative to the 19 outbound routes from the same origin, this path ranks 6th in the round. Its 1.38 ms standard deviation is 3.2% of the average RTT, slightly tighter than the route set's 3.28% median standard deviation as a share of average RTT, so London-Moscow is both well-positioned for its distance and unusually consistent in this measurement round.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **43.5 ms**                                    |
| Jitter               | **1.21 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **24.56 ms**                                   |
| Fiber Efficiency     | **56.5%**                                      |
| Latency Tier         | Excellent                                      |
| Source Region        | [Europe](/docs/network/latency/regions/europe) |
| 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 [London](https://www.geonames.org/2643743) (51.50853, -0.12574) 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                      | **2,508.5 km** |
| Vacuum RTT floor                              | **16.73 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **24.56 ms**   |
| Low-latency fiber material floor              | **24.47 ms**   |
| Engineering floor (5% path allowance)         | **25.8 ms**    |
| Research 1.33× mapped-fiber reference         | **32.67 ms**   |
| Estimated unamplified path loss               | **526.8 dB**   |
| Transparent optical spans / inline amplifiers | **33 / 32**    |
| Published RTT inflation over fiber floor      | **1.77×**      |

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        | **41.81 ms** |
| Average RTT        | **43.5 ms**  |
| Maximum RTT        | **48.52 ms** |
| Standard deviation | **1.38 ms**  |
| Stdev / average    | **3.2%**     |

## Route Context

* Departure PoP: [London (LON)](/docs/network/latency/lon-london)
* Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [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 London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms

**Fastest routes departing London (LON)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms
* [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms
* [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms
* [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 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
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms
* [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms

**Same corridor (Europe → Europe)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.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/lon-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → 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/lon-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.