# Moscow, Russia → London, UK RTT

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

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

The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to London at 100ms intervals and recorded an average round-trip time of 42.4ms, with a 40.38ms minimum and a 48.72ms maximum. Standard deviation was 1.83ms, jitter was 1.31ms, and no packets were lost.

London is the western anchor of the Northwest European corridor and Europe's traditional transatlantic gateway. Over the 2,508.5km geodesic path, the vacuum floor is 16.73ms and the fiber floor is 24.56ms; the observed average is 1.73 times the fiber floor, corresponding to a 57.9% fiber efficiency figure.

This route ranked fourth among the 19 outbound routes in the round. Its relative variability is about 4.3% of the average, above the 3.28% median ratio for the outbound route set, and the maximum was 6.32ms above the average—useful context for network planning.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **42.4 ms**                                    |
| Jitter               | **1.31 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **24.56 ms**                                   |
| Fiber Efficiency     | **57.9%**                                      |
| 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 [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). 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.73×**      |

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        | **40.38 ms** |
| Average RTT        | **42.4 ms**  |
| Maximum RTT        | **48.72 ms** |
| Standard deviation | **1.83 ms**  |
| Stdev / average    | **4.3%**     |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [London (LON)](/docs/network/latency/lon-london)
* 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**

* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 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 Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms
* [Moscow to Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms

**Fastest routes arriving at London (LON)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms

**Same corridor (Europe → Europe)**

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