Melbourne, Australia to Moscow, Russia latency report: ICMP echo round-trip time, packet loss, jitter, and fiber efficiency from the measurement round.

🇦🇺 Melbourne, Australia (MEL) → 🇷🇺 Moscow, Russia (MOW)

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

In round 2026-08-15T04:03:13Z, ICMP echo probes from Melbourne to Moscow averaged 235.9 ms across 50 samples, with a minimum of 229.28 ms and a maximum of 265 ms. The route recorded zero packet loss and remained in the fair latency tier.

The average is 1.67 times the theoretical direct-fiber floor of 141.13 ms, for a fiber efficiency of 59.8%. That larger overhead, along with jitter of 5.43 ms, indicates the path is noticeably less direct than the straight-line fiber ideal.

Among the 19 outbound routes from this Melbourne vantage point, the route ranked 12th by RTT. Its standard deviation of about 7 ms worked out to roughly 3.0% of the average, slightly calmer than the median variability of 3.08% seen across the route set.

Latency Summary

Metric	Value
RTT	235.9 ms
Jitter	5.43 ms
Packet Loss	0%
Standard Fiber Floor	141.13 ms
Fiber Efficiency	59.8%
Latency Tier	Fair
Source Region	Asia Pacific
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: MEL → MOW

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

Sample distribution: box = interquartile range (231.2–237.3 ms), median 232.8 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 (141.1 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	231.09
2	100	231.30
3	200	235.84
4	300	231.21
5	400	231.35
6	500	232.28
7	600	230.08
8	700	234.93
9	800	234.61
10	900	247.98
11	1000	235.32
12	1100	235.64
13	1200	230.77
14	1300	232.94
15	1400	232.56
16	1500	245.84
17	1600	242.93
18	1700	236.04
19	1800	235.80
20	1900	231.31
21	2000	233.14
22	2100	242.33
23	2200	235.25
24	2300	234.08
25	2400	230.49
26	2500	230.69
27	2600	231.56
28	2700	251.56
29	2800	241.56
30	2900	265.00
31	3000	247.36
32	3100	235.13
33	3200	230.43
34	3300	232.68
35	3400	230.56
36	3500	232.73
37	3600	232.38
38	3700	244.49
39	3800	241.75
40	3900	237.78
41	4000	232.61
42	4100	231.15
43	4200	230.17
44	4300	232.12
45	4400	230.55
46	4500	229.28
47	4600	237.78
48	4700	231.90
49	4800	229.47
50	4900	249.20

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 Melbourne (-37.81400, 144.96332) and Moscow (55.75204, 37.61781). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	14,412.1 km
Vacuum RTT floor	96.15 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	141.13 ms
Low-latency fiber material floor	140.57 ms
Engineering floor (5% path allowance)	148.21 ms
Research 1.33× mapped-fiber reference	187.71 ms
Estimated unamplified path loss	3026.5 dB
Transparent optical spans / inline amplifiers	190 / 189
Published RTT inflation over fiber floor	1.67×

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	229.28 ms
Average RTT	235.9 ms
Maximum RTT	265 ms
Standard deviation	7.04 ms
Stdev / average	3.0%

RTT trend

Estimated route stability across the selected time window.

Average: 236.0 ms
Minimum: 233.9 ms
Maximum: 238.3 ms
Average loss: 0.02%

Route Context

Departure PoP: Melbourne (MEL)
Destination PoP: Moscow (MOW)
Region overview: Asia Pacific → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Moscow to Melbourne latency and RTT — 236.1 ms

Fastest routes departing Melbourne (MEL)

Melbourne to Sydney latency and RTT — 9.8 ms
Melbourne to Singapore latency and RTT — 88.3 ms
Melbourne to Tokyo latency and RTT — 113.2 ms
Melbourne to Hong Kong latency and RTT — 137.4 ms
Melbourne to Taipei latency and RTT — 141.7 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28 ms
Frankfurt to Moscow latency and RTT — 34.8 ms
Amsterdam to Moscow latency and RTT — 38.2 ms
London to Moscow latency and RTT — 44.1 ms
Paris to Moscow latency and RTT — 44.5 ms

Same corridor (Asia Pacific → Europe)

Hong Kong to Moscow latency and RTT — 116.6 ms
Taipei to Moscow latency and RTT — 131.7 ms
Singapore to Marseille latency and RTT — 138.8 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/mel-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Moscow 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.

Melbourne, Australia → Moscow, Russia RTT