# Moscow, Russia → Berlin, Germany RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇩🇪 **Berlin, Germany (BER)**

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

The 2026-08-16T04:07:28Z round sent 50 ICMP echo requests from Moscow to Berlin at 100ms intervals and recorded an average round-trip time of 27.5ms, with a 26.72ms minimum and a 29.96ms maximum. The standard deviation was 0.74ms, jitter was 0.54ms, and no packets were lost.

Over the 1,613.5km geodesic path, the speed-of-light vacuum floor is 10.76ms and the fiber floor is 15.8ms. The observed average is 1.74 times the fiber floor, corresponding to a 57.5% fiber efficiency figure.

This route ranked first among the 19 outbound routes in the round. Its standard deviation of 0.74ms is about 2.7% of the average, below the 3.28% median ratio for the outbound route set, so the path combined 0% loss with unusually stable sub-millisecond variation.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **27.5 ms**                                    |
| Jitter               | **0.54 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **15.8 ms**                                    |
| Fiber Efficiency     | **57.5%**                                      |
| Latency Tier         | Ultra-Low                                      |
| 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **1,613.5 km** |
| Vacuum RTT floor                              | **10.76 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **15.8 ms**    |
| Low-latency fiber material floor              | **15.74 ms**   |
| Engineering floor (5% path allowance)         | **16.59 ms**   |
| Research 1.33× mapped-fiber reference         | **21.01 ms**   |
| Estimated unamplified path loss               | **338.8 dB**   |
| Transparent optical spans / inline amplifiers | **22 / 21**    |
| Published RTT inflation over fiber floor      | **1.74×**      |

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        | **26.72 ms** |
| Average RTT        | **27.5 ms**  |
| Maximum RTT        | **29.96 ms** |
| Standard deviation | **0.74 ms**  |
| Stdev / average    | **2.7%**     |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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**

* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms

**Fastest routes departing Moscow (MOW)**

* [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 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 Berlin (BER)**

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