# Marseille, France → Moscow, Russia RTT

🇫🇷 &#x2A;*Marseille, France (MRS)** → 🇷🇺 &#x2A;*Moscow, Russia (MOW)**

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

In round 2026-08-16T04:07:28Z, 50 ICMP probes from Marseille to Moscow returned an average round-trip time of 49.6 ms, with a minimum of 47.26 ms and a maximum of 58 ms. The 2.18 ms standard deviation and 1.92 ms jitter reflect a no-loss path whose variability keeps it in the excellent latency tier.

Among the 19 outbound routes measured from Marseille, this route ranks sixth by average latency. Its variability-to-average ratio sits above the 3.28% median across that route set, which is consistent with the much longer distance and the wider delay range captured in the sample.

The physical reference puts the Marseille-Moscow average at 1.89 times the theoretical fiber-floor latency, with a fiber-efficiency value of 52.9%. Moscow extends the backbone eastward toward European and Asia-Pacific networks, so this latency profile is particularly relevant for traffic moving between southern Europe and those farther regions. ICMP RTT is best read as a path-level indicator, not a proxy for end-user application performance.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **49.6 ms**                                    |
| Jitter               | **1.92 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **26.23 ms**                                   |
| Fiber Efficiency     | **52.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 [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) 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,678.2 km** |
| Vacuum RTT floor                              | **17.87 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **26.23 ms**   |
| Low-latency fiber material floor              | **26.12 ms**   |
| Engineering floor (5% path allowance)         | **27.54 ms**   |
| Research 1.33× mapped-fiber reference         | **34.88 ms**   |
| Estimated unamplified path loss               | **562.4 dB**   |
| Transparent optical spans / inline amplifiers | **36 / 35**    |
| Published RTT inflation over fiber floor      | **1.89×**      |

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        | **47.26 ms** |
| Average RTT        | **49.6 ms**  |
| Maximum RTT        | **58 ms**    |
| Standard deviation | **2.18 ms**  |
| Stdev / average    | **4.4%**     |

## Route Context

* Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille)
* 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 Marseille latency and RTT](/docs/network/latency/pairs/mow-mrs-rtt) — 49.9 ms

**Fastest routes departing Marseille (MRS)**

* [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms
* [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms
* [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 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
* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms

**Same corridor (Europe → Europe)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [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

## 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/mrs-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Marseille → 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/mrs-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.
