Moscow-to-Hong Kong ICMP RTT measurements: average latency, packet loss, jitter, and route efficiency for this Russia–Hong Kong Asia-Pacific path.

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

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

For the 2026-08-16T04:07:28Z ICMP echo round, Moscow to Hong Kong averaged 118.6 ms across 50 samples, with a narrow range from 116.41 ms to 127.8 ms and zero packet loss. A standard deviation of 2.24 ms and jitter of 1.64 ms make this a notably stable path.

The great-circle distance of about 7,154 km implies a fiber floor near 70.1 ms, so the observed mean is 1.69 times that floor and fiber efficiency reaches 59.1 percent. The steady sample distribution confirms the route is behaving close to its physical potential.

This route ranked 9th among 19 Moscow outbound paths, and the median variability across the Moscow outbound set was 3.28 percent of average latency. Its own standard deviation is only about 1.9 percent of the average, so latency is not just low—it is also unusually consistent for this outbound set.

Latency Summary

Metric	Value
RTT	118.6 ms
Jitter	1.64 ms
Packet Loss	0%
Standard Fiber Floor	70.05 ms
Fiber Efficiency	59.1%
Latency Tier	Good
Source Region	Europe
Destination Region	Asia Pacific

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 → HKG

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

Sample distribution: box = interquartile range (117.3–118.8 ms), median 118.1 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	116.58
2	100	116.41
3	200	119.29
4	300	117.71
5	400	117.36
6	500	116.50
7	600	116.41
8	700	118.53
9	800	118.07
10	900	121.56
11	1000	118.45
12	1100	120.15
13	1200	118.04
14	1300	120.53
15	1400	118.08
16	1500	117.59
17	1600	117.02
18	1700	119.09
19	1800	117.16
20	1900	117.32
21	2000	118.53
22	2100	118.06
23	2200	118.27
24	2300	117.85
25	2400	116.67
26	2500	119.10
27	2600	118.33
28	2700	117.81
29	2800	116.92
30	2900	118.66
31	3000	116.93
32	3100	118.58
33	3200	117.50
34	3300	118.36
35	3400	116.93
36	3500	118.34
37	3600	117.79
38	3700	117.79
39	3800	119.84
40	3900	118.79
41	4000	121.29
42	4100	125.45
43	4200	119.54
44	4300	118.07
45	4400	117.17
46	4500	117.92
47	4600	117.46
48	4700	117.32
49	4800	127.80
50	4900	125.08

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 Hong Kong (22.27832, 114.17469). 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	116.41 ms
Average RTT	118.6 ms
Maximum RTT	127.8 ms
Standard deviation	2.24 ms
Stdev / average	1.9%

RTT trend

Estimated route stability across the selected time window.

Average: 118.7 ms
Minimum: 117.4 ms
Maximum: 119.8 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Hong Kong to Moscow latency and RTT — 118.2 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27.5 ms
Moscow to Frankfurt latency and RTT — 35.9 ms
Moscow to Amsterdam latency and RTT — 37.6 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 44 ms

Fastest routes arriving at Hong Kong (HKG)

Taipei to Hong Kong latency and RTT — 15.5 ms
Singapore to Hong Kong latency and RTT — 30.8 ms
Tokyo to Hong Kong latency and RTT — 44.8 ms
Seattle to Hong Kong latency and RTT — 130.4 ms
Sydney to Hong Kong latency and RTT — 135.7 ms

Same corridor (Europe → Asia Pacific)

Moscow to Taipei latency and RTT — 132.1 ms
Marseille to Singapore latency and RTT — 139.6 ms
Berlin to Hong Kong latency and RTT — 144.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-hkg.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Hong Kong 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.

Moscow, Russia → Hong Kong RTT