Moscow, Russia to Berlin, Germany ICMP RTT page: 27 ms average, 1.32 ms jitter, 0% loss, from 50 probes in round 2026-08-15T04:03:13Z.

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

Measurement round: 2026-08-15T04:03:13Z.

The Moscow to Berlin path in round 2026-08-15T04:03:13Z averaged 27 ms across 50 ICMP echo probes sent at 100 ms intervals, with a minimum of 25.25 ms and a maximum of 30.94 ms. Jitter measured 1.32 ms, the standard deviation was 1.32 ms, and no packets were lost.

Against a geodesic distance of 1,613.5 km, the vacuum round-trip floor is 10.76 ms and the fiber floor is 15.80 ms; the observed average is 1.71 times the fiber floor, a fiber-efficiency value of 58.5 percent. The route carries an ultra-low latency tier and is ranked first among 19 outbound routes from Moscow in this round.

The nuance is variability: 1.32 ms on a 27 ms average is roughly 4.9 percent, which is above the median variability-to-average ratio of 3.08 percent across the measured route set. This is therefore a very fast route whose consistency is less exceptional than its headline latency.

Latency Summary

Metric	Value
RTT	27 ms
Jitter	1.32 ms
Packet Loss	0%
Standard Fiber Floor	15.8 ms
Fiber Efficiency	58.5%
Latency Tier	Ultra-Low
Source Region	Europe
Destination Region	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.

Ping series: MOW → BER

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 27.0 ± 0.19 ms (SE)

Sample distribution: box = interquartile range (26.0–28.1 ms), median 26.6 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.

How to read this chart

The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.

The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (15.8 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	26.42
2	100	27.24
3	200	25.78
4	300	25.67
5	400	28.58
6	500	26.22
7	600	26.61
8	700	26.25
9	800	25.78
10	900	28.25
11	1000	27.42
12	1100	29.64
13	1200	28.18
14	1300	28.54
15	1400	26.78
16	1500	28.45
17	1600	26.18
18	1700	25.81
19	1800	25.25
20	1900	26.60
21	2000	25.84
22	2100	26.04
23	2200	27.67
24	2300	30.94
25	2400	27.15
26	2500	25.86
27	2600	27.39
28	2700	28.18
29	2800	26.38
30	2900	25.45
31	3000	27.01
32	3100	29.06
33	3200	26.94
34	3300	26.09
35	3400	26.16
36	3500	25.63
37	3600	25.43
38	3700	25.40
39	3800	26.67
40	3900	26.23
41	4000	25.42
42	4100	25.98
43	4200	28.37
44	4300	26.38
45	4400	26.79
46	4500	29.25
47	4600	29.02
48	4700	26.38
49	4800	29.21
50	4900	28.03

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 for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Moscow (55.75204, 37.61781) and Berlin (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.71×

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 current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	25.25 ms
Average RTT	27 ms
Maximum RTT	30.94 ms
Standard deviation	1.32 ms
Stdev / average	4.9%

RTT trend

Estimated route stability across the selected time window.

Average: 27.0 ms
Minimum: 26.7 ms
Maximum: 27.2 ms
Average loss: 0.01%

Route Context

Departure PoP: Moscow (MOW)
Destination PoP: Berlin (BER)
Region overview: Europe → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Berlin to Moscow latency and RTT — 28 ms

Fastest routes departing Moscow (MOW)

Moscow to Frankfurt latency and RTT — 35 ms
Moscow to Amsterdam latency and RTT — 39.3 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 43.9 ms
Moscow to Marseille latency and RTT — 50.7 ms

Fastest routes arriving at Berlin (BER)

Frankfurt to Berlin latency and RTT — 6.1 ms
Amsterdam to Berlin latency and RTT — 7.2 ms
Paris to Berlin latency and RTT — 14.8 ms
London to Berlin latency and RTT — 16.2 ms
Marseille to Berlin latency and RTT — 21.5 ms

Same corridor (Europe → Europe)

Amsterdam to London latency and RTT — 5.1 ms
London to Amsterdam latency and RTT — 5.1 ms
Amsterdam to Frankfurt latency and 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. 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-15T04:03:13Z, CC BY 4.0".

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Moscow, Russia → Berlin, Germany RTT