# Moscow, Russia → Tokyo, Japan RTT

🇷🇺 **Moscow, Russia (MOW)** → 🇯🇵 **Tokyo, Japan (TYO)**

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

During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Tokyo produced an average RTT of 162.2 ms, with a minimum of 152.69 ms and a maximum of 185.56 ms. Packet loss was 0%, and jitter was 5.65 ms.

Given a geodesic distance of 7,497 km, the vacuum floor is 50.01 ms and the fiber floor is 73.42 ms. The measured average sits 2.21 times above that fiber floor, for a fiber-floor efficiency of 45.3%.

Ranked 13th of the 19 routes measured in this round, Moscow-to-Tokyo falls in the upper-middle range for latency. The standard deviation of 6.91 ms is about 4.3% of the average, above the 3.28% median standard-deviation-to-average ratio for the round, so sample-to-sample RTT varied more than was typical. All 50 probes still completed without loss, keeping the route fully responsive throughout the round.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **162.2 ms**                                               |
| Jitter               | **5.65 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **73.42 ms**                                               |
| Fiber Efficiency     | **45.3%**                                                  |
| Latency Tier         | Fair                                                       |
| 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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). It does not disclose either facility address.

| Physical Reference                            | Value         |
| --------------------------------------------- | ------------- |
| WGS-84 geodesic distance                      | **7,497 km**  |
| Vacuum RTT floor                              | **50.01 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **73.42 ms**  |
| Low-latency fiber material floor              | **73.12 ms**  |
| Engineering floor (5% path allowance)         | **77.1 ms**   |
| Research 1.33× mapped-fiber reference         | **97.64 ms**  |
| Estimated unamplified path loss               | **1574.4 dB** |
| Transparent optical spans / inline amplifiers | **99 / 98**   |
| Published RTT inflation over fiber floor      | **2.21×**     |

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        | **152.69 ms** |
| Average RTT        | **162.2 ms**  |
| Maximum RTT        | **185.56 ms** |
| Standard deviation | **6.91 ms**   |
| Stdev / average    | **4.3%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* 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**

* [Tokyo to Moscow latency and RTT](/docs/network/latency/pairs/tyo-mow-rtt) — 161.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 Tokyo (TYO)**

* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Hong Kong to Tokyo latency and RTT](/docs/network/latency/pairs/hkg-tyo-rtt) — 44.9 ms
* [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms
* [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms

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

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