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

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

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

The Moscow to Frankfurt path in round 2026-08-15T04:03:13Z averaged 35 ms from 50 ICMP echo probes, with a minimum of 34.10 ms and a maximum of 36.89 ms. A standard deviation of 0.65 ms, jitter of 0.60 ms, and zero packet loss make this a highly consistent sample.

For a geodesic distance of 2,026.8 km, the fiber floor is 19.85 ms; the measured average is 1.76 times that floor, a fiber-efficiency value of 56.7 percent. The route is rated excellent on latency and holds second position among 19 outbound routes from Moscow in this round.

Its own variability is about 1.9 percent of the average, comfortably below the median variability-to-average ratio of 3.08 percent across the measured route set. Moscow to Frankfurt pairs low absolute latency with unusually stable round-trip times in this sample.

Latency Summary

Metric	Value
RTT	35 ms
Jitter	0.6 ms
Packet Loss	0%
Standard Fiber Floor	19.85 ms
Fiber Efficiency	56.7%
Latency Tier	Excellent
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 → FRA

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

Sample distribution: box = interquartile range (34.5–35.4 ms), median 34.9 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 (19.9 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	34.38
2	100	35.37
3	200	34.99
4	300	34.40
5	400	36.12
6	500	34.87
7	600	35.14
8	700	34.71
9	800	34.55
10	900	34.34
11	1000	34.85
12	1100	34.34
13	1200	34.18
14	1300	34.22
15	1400	34.15
16	1500	34.95
17	1600	34.60
18	1700	34.85
19	1800	35.25
20	1900	34.44
21	2000	34.49
22	2100	35.70
23	2200	34.78
24	2300	34.68
25	2400	34.93
26	2500	34.56
27	2600	34.40
28	2700	35.29
29	2800	34.62
30	2900	34.22
31	3000	34.74
32	3100	34.27
33	3200	34.10
34	3300	35.93
35	3400	34.84
36	3500	34.70
37	3600	36.09
38	3700	35.63
39	3800	36.07
40	3900	35.61
41	4000	36.07
42	4100	35.84
43	4200	35.42
44	4300	35.01
45	4400	34.95
46	4500	35.63
47	4600	34.78
48	4700	36.15
49	4800	34.91
50	4900	36.89

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 Frankfurt am Main (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.76×

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	34.1 ms
Average RTT	35 ms
Maximum RTT	36.89 ms
Standard deviation	0.65 ms
Stdev / average	1.9%

RTT trend

Estimated route stability across the selected time window.

Average: 35.0 ms
Minimum: 34.7 ms
Maximum: 35.3 ms
Average loss: 0.01%

Route Context

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

Reverse direction

Frankfurt to Moscow latency and RTT — 34.8 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27 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 Frankfurt (FRA)

Amsterdam to Frankfurt latency and RTT — 5.9 ms
Berlin to Frankfurt latency and RTT — 6.1 ms
Paris to Frankfurt latency and RTT — 7.6 ms
London to Frankfurt latency and RTT — 12.3 ms
Marseille to Frankfurt latency and RTT — 17.5 ms

Same corridor (Europe → Europe)

Amsterdam to London latency and RTT — 5.1 ms
London to Amsterdam latency and RTT — 5.1 ms
Frankfurt to Amsterdam 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-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-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 → Frankfurt, Germany RTT