# Moscow, Russia → Taipei, Taiwan RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇹🇼 **Taipei, Taiwan (TPE)**

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

During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Taipei produced an average RTT of 132.1 ms, with a minimum of 126.75 ms and a maximum of 145.67 ms. No packets were lost, and jitter was 4.42 ms.

Over a geodesic distance of 7,369 km, the theoretical vacuum one-way floor is 49.16 ms and the fiber floor is 72.16 ms. The observed average is 1.83 times the fiber floor, placing the route at 54.6% fiber-floor efficiency.

Ranked 10th among the 19 routes measured in the same round, Moscow-to-Taipei sits around the middle of the set. Its standard deviation of 4.52 ms is about 3.4% of the average, just above the 3.28% median standard-deviation-to-average ratio for the round. With zero packet loss and moderate jitter, this round offers a stable baseline for Moscow-to-Taipei latency.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **132.1 ms**                                               |
| Jitter               | **4.42 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **72.16 ms**                                               |
| Fiber Efficiency     | **54.6%**                                                  |
| Latency Tier         | Good                                                       |
| Source Region        | [Europe](/docs/network/latency/regions/europe)             |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/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.

## 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 [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). It does not disclose either facility address.

| Physical Reference                            | Value         |
| --------------------------------------------- | ------------- |
| WGS-84 geodesic distance                      | **7,369 km**  |
| Vacuum RTT floor                              | **49.16 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **72.16 ms**  |
| Low-latency fiber material floor              | **71.87 ms**  |
| Engineering floor (5% path allowance)         | **75.78 ms**  |
| Research 1.33× mapped-fiber reference         | **95.98 ms**  |
| Estimated unamplified path loss               | **1547.5 dB** |
| Transparent optical spans / inline amplifiers | **97 / 96**   |
| Published RTT inflation over fiber floor      | **1.83×**     |

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        | **126.75 ms** |
| Average RTT        | **132.1 ms**  |
| Maximum RTT        | **145.67 ms** |
| Standard deviation | **4.52 ms**   |
| Stdev / average    | **3.4%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific)
* 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**

* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms

**Fastest routes departing Moscow (MOW)**

* [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms
* [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms
* [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms
* [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms

**Fastest routes arriving at Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms

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

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.6 ms
* [Berlin to Hong Kong latency and RTT](/docs/network/latency/pairs/ber-hkg-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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/mow-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Taipei 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/mow-tpe-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.