# Taipei, Taiwan → Moscow, Russia RTT

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

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

In the 2026-08-16T04:07:28Z test round, ICMP echo requests from Taipei, Taiwan to Moscow, Russia averaged 132.7 ms across 50 samples, with a minimum of 127.77 ms and a maximum of 145.28 ms. The route recorded zero packet loss and 3.84 ms jitter, consistent with its good latency tier.

The geodesic distance of about 7,369 km implies a vacuum floor of 49.16 ms and a fiber floor of 72.16 ms; the measured path runs about 1.84 times the fiber floor, or 54.4 percent fiber efficiency. Given Moscow's role as a transit corridor between European and Asia-Pacific networks, the sub-135 ms average with zero packet loss is a notable result.

Within the same 19-route outbound set, this route ranks 6th, placing it near the faster end. Its 3.91 ms standard deviation corresponds to a relative spread of about 2.9 percent, below the median variability ratio of 3.28 percent across the same set.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **132.7 ms**                                               |
| Jitter               | **3.84 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **72.16 ms**                                               |
| Fiber Efficiency     | **54.4%**                                                  |
| 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 [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) 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,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.84×**     |

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        | **127.77 ms** |
| Average RTT        | **132.7 ms**  |
| Maximum RTT        | **145.28 ms** |
| Standard deviation | **3.91 ms**   |
| Stdev / average    | **2.9%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* 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 Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms

**Fastest routes departing Taipei (TPE)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms
* [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms
* [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 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)**

* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 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/tpe-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → 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/tpe-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.