# Hong Kong → Moscow, Russia RTT

🇭🇰 **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](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Europe](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Hong Kong](https://www.geonames.org/1819729) (22.27832, 114.17469) and [Moscow](https://www.geonames.org/524901) (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](/docs/network/latency/theoretical-fiber-latency).

## 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%**      |

## Route Context

* Departure PoP: [Hong Kong (HKG)](/docs/network/latency/hkg-hong-kong)
* Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms

**Fastest routes departing Hong Kong (HKG)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.6 ms
* [Hong Kong to Sydney latency and RTT](/docs/network/latency/pairs/hkg-syd-rtt) — 137.2 ms

**Fastest routes arriving at Moscow (MOW)**

* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms
* [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms
* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms

**Same corridor (Asia Pacific → Europe)**

* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms
* [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms
* [Hong Kong to Berlin latency and RTT](/docs/network/latency/pairs/hkg-ber-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](/opendata/latency/). 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](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/hkg-mow-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.