Hong Kong → Moscow, Russia RTT
Hong Kong to Moscow ICMP RTT measurement page: average latency, packet loss, and route stability for the Hong Kong-Russia path (round 2026-08-15).
🇭🇰 Hong Kong (HKG) → 🇷🇺 Moscow, Russia (MOW)
Measurement round: 2026-08-15T04:03:13Z.
In the 2026-08-15T04:03:13Z measurement round, the ICMP echo RTT from Hong Kong to Moscow averaged 116.6 ms, with a minimum of 113.74 ms and a maximum of 130.96 ms across 50 samples. No packets were lost, and the 2.93 ms standard deviation kept jitter at 1.89 ms, placing the route in the Good latency tier.
The geodesic separation is 7,153.6 km, giving a theoretical fiber-floor RTT of 70.05 ms; the observed average is 1.66 times that floor, or 60.1% fiber efficiency. That means the route retains a meaningful portion of the speed-of-light budget while still allowing for realistic network overhead on a transcontinental path.
Within the 19-route peer set, this outbound route ranked 4th, so most comparable paths had higher average RTTs in this round. Its standard-deviation-to-average ratio was 2.51%, below the peer-set median of 3.08%, and the spread between minimum and maximum was 17.22 ms — a sign that the route is both comparatively fast and consistent.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 116.6 ms |
| Jitter | 1.89 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 70.05 ms |
| Fiber Efficiency | 60.1% |
| 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-15T04:03:13Z · avg 116.6 ± 0.41 ms (SE)
Sample distribution: box = interquartile range (114.9–117.2 ms), median 116.0 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 | 117.55 |
| 2 | 100 | 117.08 |
| 3 | 200 | 115.20 |
| 4 | 300 | 116.41 |
| 5 | 400 | 115.05 |
| 6 | 500 | 113.96 |
| 7 | 600 | 113.81 |
| 8 | 700 | 113.74 |
| 9 | 800 | 115.96 |
| 10 | 900 | 114.46 |
| 11 | 1000 | 115.21 |
| 12 | 1100 | 115.02 |
| 13 | 1200 | 113.98 |
| 14 | 1300 | 116.27 |
| 15 | 1400 | 115.75 |
| 16 | 1500 | 117.15 |
| 17 | 1600 | 114.82 |
| 18 | 1700 | 116.00 |
| 19 | 1800 | 114.65 |
| 20 | 1900 | 115.88 |
| 21 | 2000 | 115.32 |
| 22 | 2100 | 114.79 |
| 23 | 2200 | 115.42 |
| 24 | 2300 | 118.32 |
| 25 | 2400 | 116.02 |
| 26 | 2500 | 119.80 |
| 27 | 2600 | 116.89 |
| 28 | 2700 | 117.51 |
| 29 | 2800 | 115.03 |
| 30 | 2900 | 115.48 |
| 31 | 3000 | 130.96 |
| 32 | 3100 | 126.07 |
| 33 | 3200 | 120.01 |
| 34 | 3300 | 119.07 |
| 35 | 3400 | 117.19 |
| 36 | 3500 | 115.72 |
| 37 | 3600 | 116.00 |
| 38 | 3700 | 118.52 |
| 39 | 3800 | 117.10 |
| 40 | 3900 | 114.76 |
| 41 | 4000 | 114.10 |
| 42 | 4100 | 114.09 |
| 43 | 4200 | 116.33 |
| 44 | 4300 | 114.46 |
| 45 | 4400 | 117.15 |
| 46 | 4500 | 114.79 |
| 47 | 4600 | 118.09 |
| 48 | 4700 | 117.65 |
| 49 | 4800 | 116.83 |
| 50 | 4900 | 118.58 |
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.
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 () | 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.66× |
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 | 113.74 ms |
| Average RTT | 116.6 ms |
| Maximum RTT | 130.96 ms |
| Standard deviation | 2.93 ms |
| Stdev / average | 2.5% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 116.5 ms
- Minimum
- 115.3 ms
- Maximum
- 117.6 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
Related City-Pair Routes
Reverse direction
- Moscow to Hong Kong latency and RTT — 118.5 ms
Fastest routes departing Hong Kong (HKG)
- Hong Kong to Taipei latency and RTT — 15.2 ms
- Hong Kong to Singapore latency and RTT — 31.2 ms
- Hong Kong to Tokyo latency and RTT — 45 ms
- Hong Kong to Seattle latency and RTT — 129.9 ms
- Hong Kong to Sydney latency and RTT — 136.3 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)
- Taipei to Moscow latency and RTT — 131.7 ms
- Singapore to Marseille latency and RTT — 138.8 ms
- Hong Kong to Berlin latency and RTT — 143.6 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-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.