Berlin to Moscow Latency, Ping & RTT | AS203314
Berlin to Moscow ping and RTT: 28.5 ms, 0.19 ms jitter, 15.8 ms fiber floor, and 55.4% efficiency across AS203314. Updated 2026-07-19.
🇩🇪 This page compares the published ping and round-trip time (RTT) from Berlin (BER) to 🇷🇺 Moscow (MOW) with vacuum and optical-fiber physical limits.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 28.5 ms |
| Jitter | 0.19 ms |
| Packet Loss | 0.12% |
| Standard Fiber Floor | 15.8 ms |
| Fiber Efficiency | 55.4% |
| Latency Tier | Ultra-Low |
| Source Region | Europe |
| Destination Region | Europe |
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Berlin (52.52437, 13.41053) and Moscow (55.75204, 37.61781). 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 () | 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.8× |
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 following estimated indicators summarize route stability for the current publication period and are intended for comparative planning rather than SLA evaluation.
| Stability Indicator | Value |
|---|---|
| Minimum RTT | 28.3 ms |
| Median RTT (p50) | 28.5 ms |
| 95th percentile RTT (p95) | 28.7 ms |
| Maximum RTT | 28.9 ms |
| Jitter | 0.19 ms |
| Packet loss | 0.12% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 28.5 ms
- Minimum
- 28.2 ms
- Maximum
- 28.8 ms
- Average loss
- 0.04%
Route Context
- Departure PoP: Berlin (BER)
- 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 Berlin latency and RTT — 26.8 ms
- Berlin to Frankfurt latency and RTT — 6.1 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Berlin to Paris latency and RTT — 15.1 ms
- Berlin to London latency and RTT — 15.9 ms
- Berlin to Marseille latency and RTT — 20.2 ms
About This Measurement
Published RTT reflects best-case backbone path behavior. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. Stability indicators are comparative estimates, and none of these values is an SLA.
Data auto-generated on July 19, 2026. Explore the full interactive latency matrix or browse more city-pair routes.