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

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

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

For the 2026-08-15T04:03:13Z round, Moscow-to-Hong Kong ICMP echo samples averaged 118.5 ms RTT, with a tight range of 114.56 ms to 130.22 ms across all 50 probes and no packet loss.

That result is about 1.69 times the theoretical fiber floor for the 7,153.6 km great-circle path, corresponding to 59.1% direct-line fiber efficiency. The 3.33 ms standard deviation and 2.74 ms jitter are low, and the route's latency tier is Good.

This path ranked 9th among 19 outbound routes from Moscow in this round, placing it near the middle of the group. Its relative variability of about 2.8% is below the network's median relative variability of 3.08%, indicating a stable route with minimal fluctuation around the 118.5 ms average.

Latency Summary

Metric	Value
RTT	118.5 ms
Jitter	2.74 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-15T04:03:13Z · avg 118.5 ± 0.47 ms (SE)

Sample distribution: box = interquartile range (115.9–119.8 ms), median 117.5 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	114.56
2	100	115.16
3	200	115.31
4	300	123.23
5	400	130.22
6	500	121.37
7	600	117.36
8	700	117.00
9	800	118.87
10	900	118.26
11	1000	115.85
12	1100	115.30
13	1200	115.45
14	1300	116.07
15	1400	115.79
16	1500	120.16
17	1600	122.25
18	1700	119.68
19	1800	126.10
20	1900	118.50
21	2000	117.33
22	2100	115.84
23	2200	117.82
24	2300	117.19
25	2400	124.41
26	2500	120.26
27	2600	116.45
28	2700	125.62
29	2800	119.83
30	2900	117.08
31	3000	115.83
32	3100	117.01
33	3200	124.86
34	3300	119.77
35	3400	122.23
36	3500	118.92
37	3600	118.16
38	3700	119.86
39	3800	118.06
40	3900	115.75
41	4000	115.10
42	4100	117.12
43	4200	117.02
44	4300	117.61
45	4400	116.44
46	4500	118.33
47	4600	117.69
48	4700	116.78
49	4800	115.36
50	4900	114.78

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

Round Statistic	Value
Minimum RTT	114.56 ms
Average RTT	118.5 ms
Maximum RTT	130.22 ms
Standard deviation	3.33 ms
Stdev / average	2.8%

RTT trend

Estimated route stability across the selected time window.

Average: 118.3 ms
Minimum: 117.5 ms
Maximum: 119.2 ms
Average loss: 0.02%

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 — 116.6 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27 ms
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

Fastest routes arriving at Hong Kong (HKG)

Taipei to Hong Kong latency and RTT — 15.4 ms
Singapore to Hong Kong latency and RTT — 30.9 ms
Tokyo to Hong Kong latency and RTT — 45.6 ms
Seattle to Hong Kong latency and RTT — 130.7 ms
Sydney to Hong Kong latency and RTT — 135.9 ms

Same corridor (Europe → Asia Pacific)

Moscow to Taipei latency and RTT — 130.9 ms
Marseille to Singapore latency and RTT — 138.5 ms
Berlin to Hong Kong latency and RTT — 143.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-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 → Hong Kong RTT