# Moscow, Russia → Frankfurt, Germany RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇩🇪 **Frankfurt, Germany (FRA)**

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

The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to Frankfurt at 100ms intervals and recorded an average round-trip time of 35.9ms, with a 33.56ms minimum and a 42.93ms maximum. Standard deviation was 1.78ms, jitter was 1.52ms, and no packets were lost.

Frankfurt is a central switching point of the European fiber ring. For the 2,026.8km geodesic path, the vacuum floor is 13.52ms and the fiber floor is 19.85ms; the observed average is 1.81 times that fiber floor, with a 55.3% fiber efficiency figure.

This route ranked second among the 19 outbound routes, but its relative variability is about 5.0% of the average, above the 3.28% median ratio for the outbound route set. The 9.37ms gap between the minimum and maximum shows that individual probes varied more than the route's strong rank alone might suggest.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **35.9 ms**                                    |
| Jitter               | **1.52 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **19.85 ms**                                   |
| Fiber Efficiency     | **55.3%**                                      |
| 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 [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **2,026.8 km** |
| Vacuum RTT floor                              | **13.52 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **19.85 ms**   |
| Low-latency fiber material floor              | **19.77 ms**   |
| Engineering floor (5% path allowance)         | **20.84 ms**   |
| Research 1.33× mapped-fiber reference         | **26.4 ms**    |
| Estimated unamplified path loss               | **425.6 dB**   |
| Transparent optical spans / inline amplifiers | **27 / 26**    |
| Published RTT inflation over fiber floor      | **1.81×**      |

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        | **33.56 ms** |
| Average RTT        | **35.9 ms**  |
| Maximum RTT        | **42.93 ms** |
| Standard deviation | **1.78 ms**  |
| Stdev / average    | **5.0%**     |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* 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**

* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms

**Fastest routes departing Moscow (MOW)**

* [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms
* [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 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 Frankfurt (FRA)**

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