London, UK → Moscow, Russia RTT
London to Moscow ICMP RTT page: average round-trip time, minimum/maximum latency, jitter and packet loss for the UK-Russia route in round 2026-08-16T04:07:28Z.
🇬🇧 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 |
| Destination Region | 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.
Ping series: LON → MOW
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 43.5 ± 0.20 ms (SE)
Sample distribution: box = interquartile range (42.5–44.0 ms), median 43.2 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (24.6 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 42.59 |
| 2 | 100 | 43.66 |
| 3 | 200 | 42.41 |
| 4 | 300 | 42.07 |
| 5 | 400 | 42.68 |
| 6 | 500 | 42.51 |
| 7 | 600 | 45.92 |
| 8 | 700 | 43.25 |
| 9 | 800 | 43.41 |
| 10 | 900 | 44.05 |
| 11 | 1000 | 42.58 |
| 12 | 1100 | 42.09 |
| 13 | 1200 | 43.60 |
| 14 | 1300 | 42.42 |
| 15 | 1400 | 42.07 |
| 16 | 1500 | 45.46 |
| 17 | 1600 | 43.78 |
| 18 | 1700 | 43.85 |
| 19 | 1800 | 42.74 |
| 20 | 1900 | 46.59 |
| 21 | 2000 | 43.88 |
| 22 | 2100 | 43.73 |
| 23 | 2200 | 43.05 |
| 24 | 2300 | 43.29 |
| 25 | 2400 | 43.09 |
| 26 | 2500 | 42.82 |
| 27 | 2600 | 42.19 |
| 28 | 2700 | 42.10 |
| 29 | 2800 | 41.94 |
| 30 | 2900 | 41.81 |
| 31 | 3000 | 41.87 |
| 32 | 3100 | 42.81 |
| 33 | 3200 | 42.29 |
| 34 | 3300 | 44.94 |
| 35 | 3400 | 48.52 |
| 36 | 3500 | 46.66 |
| 37 | 3600 | 43.64 |
| 38 | 3700 | 42.47 |
| 39 | 3800 | 43.31 |
| 40 | 3900 | 44.71 |
| 41 | 4000 | 42.86 |
| 42 | 4100 | 44.73 |
| 43 | 4200 | 43.27 |
| 44 | 4300 | 44.28 |
| 45 | 4400 | 42.88 |
| 46 | 4500 | 44.32 |
| 47 | 4600 | 45.27 |
| 48 | 4700 | 44.47 |
| 49 | 4800 | 43.24 |
| 50 | 4900 | 42.83 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for London (51.50853, -0.12574) and Moscow (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 () | 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.
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% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 43.5 ms
- Minimum
- 43.1 ms
- Maximum
- 44.0 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: London (LON)
- Destination PoP: Moscow (MOW)
- Region overview: Europe → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Moscow to London latency and RTT — 42.4 ms
Fastest routes departing London (LON)
- London to Amsterdam latency and RTT — 5.2 ms
- London to Paris latency and RTT — 6.4 ms
- London to Frankfurt latency and RTT — 13.6 ms
- London to Berlin latency and RTT — 16.2 ms
- London to Marseille latency and RTT — 17.9 ms
Fastest routes arriving at Moscow (MOW)
- Berlin to Moscow latency and RTT — 28.6 ms
- Frankfurt to Moscow latency and RTT — 34.7 ms
- Amsterdam to Moscow latency and RTT — 38.1 ms
- Paris to Moscow latency and RTT — 44.7 ms
- Marseille to Moscow latency and RTT — 49.6 ms
Same corridor (Europe → Europe)
- Amsterdam to London latency and RTT — 5.2 ms
- Amsterdam to Frankfurt latency and RTT — 5.9 ms
- Frankfurt to Amsterdam latency and 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. 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 or browse more city-pair routes.