# Paris, France → Moscow, Russia RTT

🇫🇷 **Paris, France (PAR)** → 🇷🇺 **Moscow, Russia (MOW)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Paris to Moscow averaged 44.7 ms across 50 samples, with a minimum of 43.04 ms and a maximum of 51.46 ms. No packets were lost, and jitter was 1.18 ms.

This route ranked sixth among the 19 outbound routes from Paris measured in the same round. The 1.56 ms standard deviation on the 44.7 ms average is a relative spread of about 3.5%, close to the 3.3% median for that route set.

For the 2,494 km great-circle distance, the theoretical fiber floor is 24.42 ms; the measured average is about 1.83 times that floor, or 54.6% fiber efficiency. The zero-loss result and the bounded 43.04 to 51.46 ms range indicate a stable long-haul path, consistent with Moscow's role as an eastward backbone transit corridor toward Asia-Pacific networks.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **44.7 ms**                                    |
| Jitter               | **1.18 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **24.42 ms**                                   |
| Fiber Efficiency     | **54.6%**                                      |
| 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 [Paris](https://www.geonames.org/2988507) (48.85341, 2.34880) 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,494.1 km** |
| Vacuum RTT floor                              | **16.64 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **24.42 ms**   |
| Low-latency fiber material floor              | **24.33 ms**   |
| Engineering floor (5% path allowance)         | **25.65 ms**   |
| Research 1.33× mapped-fiber reference         | **32.48 ms**   |
| Estimated unamplified path loss               | **523.8 dB**   |
| Transparent optical spans / inline amplifiers | **33 / 32**    |
| Published RTT inflation over fiber floor      | **1.83×**      |

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        | **43.04 ms** |
| Average RTT        | **44.7 ms**  |
| Maximum RTT        | **51.46 ms** |
| Standard deviation | **1.56 ms**  |
| Stdev / average    | **3.5%**     |

## Route Context

* Departure PoP: [Paris (PAR)](/docs/network/latency/par-paris)
* 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 Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms

**Fastest routes departing Paris (PAR)**

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