# 🇷🇺 Moscow Ping & Network Latency (MOW) | AS203314

## 🇷🇺 Moscow (MOW)

Moscow anchors Hats Network's reach into Eastern Europe and Central Asia, providing a critical transit corridor between European and Asia-Pacific networks.

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

This page provides round-trip time (RTT) latency metrics between the **Moscow (MOW)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Moscow, Russia (Europe)
* **Region:** Europe
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 524901](https://www.geonames.org/524901) — 55.75204, 37.61781
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** MOW1
* **Upstream transit:** RETN / Melbicom

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                      |
| --------------------- | ---------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇷🇺 Moscow (MOW) → 🇩🇪 Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt) (**27.5 ms**) — Ultra-Low |
| Slowest Route         | [🇷🇺 Moscow (MOW) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/mow-syd-rtt) (**241.8 ms**)            |
| Average RTT           | **126.3 ms**                                                                                               |
| Average Jitter        | **1.03 ms**                                                                                                |
| Average Packet Loss   | **0.06%**                                                                                                  |
| Best Fiber Efficiency | **68.6%**                                                                                                  |
| Intra-Region Peers    | 6 PoPs in Europe                                                                                           |
| Total Routes          | 19 outbound / 19 inbound (100% coverage)                                                                   |

> Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the [theoretical fiber latency methodology](/docs/network/latency/theoretical-fiber-latency).

## Geographic & Network Position

Moscow sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **27.5 ms** (Berlin (BER)) to **49.9 ms** (Marseille (MRS)).

Moscow extends the backbone eastward, providing a transit corridor between European and Asia-Pacific networks.

## Outbound Latency from Moscow (MOW)

Round-trip time in milliseconds **from Moscow** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇩🇪 Berlin (BER)       | **[27.5](/docs/network/latency/pairs/mow-ber-rtt)**  | 15.8 ms     | 57.5%      | 0.3 ms  | 0.13% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[35.9](/docs/network/latency/pairs/mow-fra-rtt)**  | 19.85 ms    | 55.3%      | 0.3 ms  | 0%    | Excellent |
| 🇳🇱 Amsterdam (AMS)    | **[37.6](/docs/network/latency/pairs/mow-ams-rtt)**  | 21.1 ms     | 56.1%      | 0.28 ms | 0.17% | Excellent |
| 🇬🇧 London (LON)       | **[42.4](/docs/network/latency/pairs/mow-lon-rtt)**  | 24.56 ms    | 57.9%      | 0.46 ms | 0.18% | Excellent |
| 🇫🇷 Paris (PAR)        | **[44](/docs/network/latency/pairs/mow-par-rtt)**    | 24.42 ms    | 55.5%      | 0.29 ms | 0%    | Excellent |
| 🇫🇷 Marseille (MRS)    | **[49.9](/docs/network/latency/pairs/mow-mrs-rtt)**  | 26.23 ms    | 52.6%      | 0.4 ms  | 0.05% | Excellent |
| 🇺🇸 New York (NYC)     | **[107.5](/docs/network/latency/pairs/mow-nyc-rtt)** | 73.75 ms    | 68.6%      | 1 ms    | 0%    | Good      |
| 🇺🇸 Ashburn (IAD)      | **[113.9](/docs/network/latency/pairs/mow-iad-rtt)** | 76.88 ms    | 67.5%      | 1 ms    | 0.08% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[118.6](/docs/network/latency/pairs/mow-hkg-rtt)** | 70.05 ms    | 59.1%      | 0.77 ms | 0.13% | Good      |
| 🇹🇼 Taipei (TPE)       | **[132.1](/docs/network/latency/pairs/mow-tpe-rtt)** | 72.16 ms    | 54.6%      | 1.49 ms | 0%    | Good      |
| 🇺🇸 Miami (MIA)        | **[144.5](/docs/network/latency/pairs/mow-mia-rtt)** | 90.48 ms    | 62.6%      | 1.25 ms | 0.07% | Good      |
| 🇸🇬 Singapore (SIN)    | **[147.3](/docs/network/latency/pairs/mow-sin-rtt)** | 82.49 ms    | 56%        | 1.11 ms | 0.17% | Good      |
| 🇯🇵 Tokyo (TYO)        | **[162.2](/docs/network/latency/pairs/mow-tyo-rtt)** | 73.42 ms    | 45.3%      | 1.92 ms | 0.08% | Fair      |
| 🇺🇸 Seattle (SEA)      | **[164.8](/docs/network/latency/pairs/mow-sea-rtt)** | 82.23 ms    | 49.9%      | 0.99 ms | 0%    | Fair      |
| 🇺🇸 Los Angeles (LAX)  | **[177.7](/docs/network/latency/pairs/mow-lax-rtt)** | 95.9 ms     | 54%        | 1.55 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[201.9](/docs/network/latency/pairs/mow-jnb-rtt)** | 89.37 ms    | 44.3%      | 1.29 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[214.4](/docs/network/latency/pairs/mow-gru-rtt)** | 115.47 ms   | 53.9%      | 1.47 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[235.9](/docs/network/latency/pairs/mow-mel-rtt)** | 141.13 ms   | 59.8%      | 1.11 ms | 0%    | Fair      |
| 🇦🇺 Sydney (SYD)       | **[241.8](/docs/network/latency/pairs/mow-syd-rtt)** | 141.84 ms   | 58.7%      | 2.66 ms | 0%    | Fair      |

## Fastest Routes to Moscow (MOW)

The 10 fastest measured routes **to Moscow**, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.

| Rank | Source               | Avg RTT                                                 | Min       | Max       | Stdev   |
| ---- | -------------------- | ------------------------------------------------------- | --------- | --------- | ------- |
| 1    | 🇩🇪 Berlin (BER)    | **[28.6 ms](/docs/network/latency/pairs/ber-mow-rtt)**  | 27.35 ms  | 31.58 ms  | 1.1 ms  |
| 2    | 🇩🇪 Frankfurt (FRA) | **[34.7 ms](/docs/network/latency/pairs/fra-mow-rtt)**  | 32.66 ms  | 40.02 ms  | 1.68 ms |
| 3    | 🇳🇱 Amsterdam (AMS) | **[38.1 ms](/docs/network/latency/pairs/ams-mow-rtt)**  | 35.69 ms  | 44.57 ms  | 1.9 ms  |
| 4    | 🇬🇧 London (LON)    | **[43.5 ms](/docs/network/latency/pairs/lon-mow-rtt)**  | 41.81 ms  | 48.52 ms  | 1.38 ms |
| 5    | 🇫🇷 Paris (PAR)     | **[44.7 ms](/docs/network/latency/pairs/par-mow-rtt)**  | 43.04 ms  | 51.46 ms  | 1.56 ms |
| 6    | 🇫🇷 Marseille (MRS) | **[49.6 ms](/docs/network/latency/pairs/mrs-mow-rtt)**  | 47.26 ms  | 58 ms     | 2.18 ms |
| 7    | 🇺🇸 New York (NYC)  | **[107 ms](/docs/network/latency/pairs/nyc-mow-rtt)**   | 101.46 ms | 119.28 ms | 4.26 ms |
| 8    | 🇺🇸 Ashburn (IAD)   | **[112.8 ms](/docs/network/latency/pairs/iad-mow-rtt)** | 109.18 ms | 122.64 ms | 3.63 ms |
| 9    | 🇭🇰 Hong Kong (HKG) | **[118.2 ms](/docs/network/latency/pairs/hkg-mow-rtt)** | 115.72 ms | 128.25 ms | 2.23 ms |
| 10   | 🇹🇼 Taipei (TPE)    | **[132.7 ms](/docs/network/latency/pairs/tpe-mow-rtt)** | 127.77 ms | 145.28 ms | 3.91 ms |

## Inbound Latency to Moscow (MOW)

Round-trip time in milliseconds **from all other PoPs to Moscow**. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.

| Source                  | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇩🇪 Berlin (BER)       | **[28.6](/docs/network/latency/pairs/ber-mow-rtt)**  | 15.8 ms     | 55.2%      | 0.33 ms | 0%    | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[34.7](/docs/network/latency/pairs/fra-mow-rtt)**  | 19.85 ms    | 57.2%      | 0.25 ms | 0.13% | Excellent |
| 🇳🇱 Amsterdam (AMS)    | **[38.1](/docs/network/latency/pairs/ams-mow-rtt)**  | 21.1 ms     | 55.4%      | 0.38 ms | 0%    | Excellent |
| 🇬🇧 London (LON)       | **[43.5](/docs/network/latency/pairs/lon-mow-rtt)**  | 24.56 ms    | 56.5%      | 0.2 ms  | 0.06% | Excellent |
| 🇫🇷 Paris (PAR)        | **[44.7](/docs/network/latency/pairs/par-mow-rtt)**  | 24.42 ms    | 54.6%      | 0.23 ms | 0.2%  | Excellent |
| 🇫🇷 Marseille (MRS)    | **[49.6](/docs/network/latency/pairs/mrs-mow-rtt)**  | 26.23 ms    | 52.9%      | 0.45 ms | 0.07% | Excellent |
| 🇺🇸 New York (NYC)     | **[107](/docs/network/latency/pairs/nyc-mow-rtt)**   | 73.75 ms    | 68.9%      | 1.08 ms | 0.06% | Good      |
| 🇺🇸 Ashburn (IAD)      | **[112.8](/docs/network/latency/pairs/iad-mow-rtt)** | 76.88 ms    | 68.2%      | 0.79 ms | 0.13% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[118.2](/docs/network/latency/pairs/hkg-mow-rtt)** | 70.05 ms    | 59.3%      | 1.17 ms | 0.11% | Good      |
| 🇹🇼 Taipei (TPE)       | **[132.7](/docs/network/latency/pairs/tpe-mow-rtt)** | 72.16 ms    | 54.4%      | 0.68 ms | 0.09% | Good      |
| 🇺🇸 Miami (MIA)        | **[145.5](/docs/network/latency/pairs/mia-mow-rtt)** | 90.48 ms    | 62.2%      | 1.67 ms | 0.13% | Good      |
| 🇸🇬 Singapore (SIN)    | **[147.7](/docs/network/latency/pairs/sin-mow-rtt)** | 82.49 ms    | 55.8%      | 0.99 ms | 0.11% | Good      |
| 🇯🇵 Tokyo (TYO)        | **[161.7](/docs/network/latency/pairs/tyo-mow-rtt)** | 73.42 ms    | 45.4%      | 1.62 ms | 0.09% | Fair      |
| 🇺🇸 Seattle (SEA)      | **[164.6](/docs/network/latency/pairs/sea-mow-rtt)** | 82.23 ms    | 50%        | 1.42 ms | 0%    | Fair      |
| 🇺🇸 Los Angeles (LAX)  | **[177](/docs/network/latency/pairs/lax-mow-rtt)**   | 95.9 ms     | 54.2%      | 1.7 ms  | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[200.7](/docs/network/latency/pairs/jnb-mow-rtt)** | 89.37 ms    | 44.5%      | 2.17 ms | 0.16% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[219.5](/docs/network/latency/pairs/gru-mow-rtt)** | 115.47 ms   | 52.6%      | 1.57 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[236.1](/docs/network/latency/pairs/mel-mow-rtt)** | 141.13 ms   | 59.8%      | 2.48 ms | 0.05% | Fair      |
| 🇦🇺 Sydney (SYD)       | **[242.2](/docs/network/latency/pairs/syd-mow-rtt)** | 141.84 ms   | 58.6%      | 1.9 ms  | 0.11% | Fair      |

## Europe Peers

Moscow is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity.

| PoP                                     | Code | Country     | RTT (ms) | Tier      |
| --------------------------------------- | ---- | ----------- | -------- | --------- |
| [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS  | Netherlands | **37.6** | Excellent |
| [🇩🇪 Berlin (BER)](./ber-berlin)       | BER  | Germany     | **27.5** | Ultra-Low |
| [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA  | Germany     | **35.9** | Excellent |
| [🇬🇧 London (LON)](./lon-london)       | LON  | UK          | **42.4** | Excellent |
| [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS  | France      | **49.9** | Excellent |
| [🇫🇷 Paris (PAR)](./par-paris)         | PAR  | France      | **44**   | Excellent |

## Frequently Asked Questions

**What is the fastest route to Moscow?**

The fastest measured route to Moscow (MOW) is [Berlin (BER) → Moscow (MOW)](/docs/network/latency/pairs/ber-mow-rtt), averaging **28.6 ms** RTT (Ultra-Low).

**What is the fastest route from Moscow?**

The fastest measured route from Moscow (MOW) is [Moscow (MOW) → Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt), averaging **27.5 ms** RTT (Ultra-Low).

**How well connected is Moscow to the Hats Network backbone?**

Moscow (MOW) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Moscow (MOW) → Sydney (SYD)](/docs/network/latency/pairs/mow-syd-rtt), averages **241.8 ms** RTT.

## Open Data

Measured latency data for Moscow (MOW) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) as part of the Hats Network open latency dataset:

* **Per-route files** — every directed route from Moscow is published as `mow-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [mow-ber.pings.csv](/opendata/latency/latest/pairs/mow-ber.pings.csv), the 50-probe ICMP echo round for [Moscow (MOW) → Berlin (BER)](/docs/network/latency/pairs/mow-ber-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/mow-moscow).
- **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.