ICMP RTT page for Hong Kong, Hong Kong to Moscow, Russia: 50-probe latency stats, jitter, packet loss, and fiber-floor efficiency for the route.

🇭🇰 Hong Kong (HKG) → 🇷🇺 Moscow, Russia (MOW)

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

The 2026-08-16T04:07:28Z measurement round sent 50 ICMP echo probes from Hong Kong to Moscow at 100 ms intervals, and all probes came back, so packet loss was 0 percent. The average RTT was 118.2 ms, with a minimum of 115.72 ms and a maximum of 128.25 ms.

A 2.23 ms standard deviation and 1.78 ms jitter keep this route inside a tight band, matching its Good latency tier. It ranks fourth among the 19 outbound routes measured from Hong Kong in this round, and its variation coefficient is well below the 3.28 percent median for that outbound set.

The great-circle distance is 7,153.6 km, which puts the theoretical fiber-floor RTT at 70.05 ms; the measured 118.2 ms average is 1.69 times that floor, for a fiber efficiency of 59.3 percent. Zero loss and low variance make this a steady network-layer path, though ICMP RTT alone is not a predictor of end-user application performance.

Latency Summary

Metric	Value
RTT	118.2 ms
Jitter	1.78 ms
Packet Loss	0%
Standard Fiber Floor	70.05 ms
Fiber Efficiency	59.3%
Latency Tier	Good
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: HKG → MOW

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 118.2 ± 0.32 ms (SE)

Sample distribution: box = interquartile range (116.7–118.8 ms), median 117.7 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 (70.0 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	128.25
2	100	121.84
3	200	118.06
4	300	118.82
5	400	117.85
6	500	118.68
7	600	116.49
8	700	115.74
9	800	116.37
10	900	122.17
11	1000	119.65
12	1100	118.54
13	1200	121.19
14	1300	117.31
15	1400	115.98
16	1500	120.84
17	1600	118.54
18	1700	121.22
19	1800	118.38
20	1900	119.68
21	2000	117.12
22	2100	117.42
23	2200	118.71
24	2300	116.49
25	2400	115.72
26	2500	116.27
27	2600	117.42
28	2700	117.86
29	2800	121.34
30	2900	118.84
31	3000	117.41
32	3100	116.62
33	3200	117.74
34	3300	116.58
35	3400	115.82
36	3500	117.65
37	3600	116.90
38	3700	117.78
39	3800	116.37
40	3900	116.47
41	4000	116.91
42	4100	116.10
43	4200	117.06
44	4300	116.93
45	4400	121.72
46	4500	117.81
47	4600	118.80
48	4700	117.99
49	4800	117.03
50	4900	117.52

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 Hong Kong (22.27832, 114.17469) and Moscow (55.75204, 37.61781). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	7,153.6 km
Vacuum RTT floor	47.72 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	70.05 ms
Low-latency fiber material floor	69.77 ms
Engineering floor (5% path allowance)	73.57 ms
Research 1.33× mapped-fiber reference	93.17 ms
Estimated unamplified path loss	1502.3 dB
Transparent optical spans / inline amplifiers	94 / 93
Published RTT inflation over fiber floor	1.69×

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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	115.72 ms
Average RTT	118.2 ms
Maximum RTT	128.25 ms
Standard deviation	2.23 ms
Stdev / average	1.9%

RTT trend

Estimated route stability across the selected time window.

Average: 118.2 ms
Minimum: 117.3 ms
Maximum: 119.5 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Moscow to Hong Kong latency and RTT — 118.6 ms

Fastest routes departing Hong Kong (HKG)

Hong Kong to Taipei latency and RTT — 14.7 ms
Hong Kong to Singapore latency and RTT — 31.5 ms
Hong Kong to Tokyo latency and RTT — 44.9 ms
Hong Kong to Seattle latency and RTT — 131.6 ms
Hong Kong to Sydney latency and RTT — 137.2 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28.6 ms
Frankfurt to Moscow latency and RTT — 34.7 ms
Amsterdam to Moscow latency and RTT — 38.1 ms
London to Moscow latency and RTT — 43.5 ms
Paris to Moscow latency and RTT — 44.7 ms

Same corridor (Asia Pacific → Europe)

Taipei to Moscow latency and RTT — 132.7 ms
Singapore to Marseille latency and RTT — 140.6 ms
Hong Kong to Berlin latency and RTT — 145.1 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/hkg-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Hong Kong → Moscow round 2026-08-16T04:07:28Z, CC BY 4.0".

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

Hong Kong → Moscow, Russia RTT