ICMP RTT measurements between Moscow, Russia and Tokyo, Japan: average latency, jitter, packet loss, and route efficiency for the round.

🇷🇺 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
Destination Region	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.

Ping series: MOW → TYO

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 162.2 ± 0.98 ms (SE)

Sample distribution: box = interquartile range (157.5–163.9 ms), median 161.2 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.

How to read this chart

The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.

The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (73.4 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	154.94
2	100	161.38
3	200	183.72
4	300	166.21
5	400	156.94
6	500	160.14
7	600	154.85
8	700	152.69
9	800	158.74
10	900	161.32
11	1000	157.06
12	1100	163.95
13	1200	158.45
14	1300	154.68
15	1400	155.02
16	1500	159.38
17	1600	162.00
18	1700	158.59
19	1800	155.87
20	1900	155.98
21	2000	163.45
22	2100	156.12
23	2200	161.91
24	2300	157.28
25	2400	164.78
26	2500	159.72
27	2600	163.28
28	2700	158.50
29	2800	157.77
30	2900	157.48
31	3000	163.43
32	3100	156.32
33	3200	157.64
34	3300	159.04
35	3400	161.76
36	3500	165.95
37	3600	163.63
38	3700	170.08
39	3800	178.73
40	3900	171.16
41	4000	185.56
42	4100	165.42
43	4200	169.77
44	4300	159.92
45	4400	162.30
46	4500	161.71
47	4600	160.99
48	4700	170.53
49	4800	171.90
50	4900	161.96

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 for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Moscow (55.75204, 37.61781) and Tokyo (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.

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%

RTT trend

Estimated route stability across the selected time window.

Average: 162.1 ms
Minimum: 160.6 ms
Maximum: 163.3 ms
Average loss: 0.02%

Route Context

Departure PoP: Moscow (MOW)
Destination PoP: Tokyo (TYO)
Region overview: Europe → Asia Pacific
Corridor overview: Europe to Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Tokyo to Moscow latency and RTT — 161.7 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27.5 ms
Moscow to Frankfurt latency and RTT — 35.9 ms
Moscow to Amsterdam latency and RTT — 37.6 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 44 ms

Fastest routes arriving at Tokyo (TYO)

Taipei to Tokyo latency and RTT — 31.9 ms
Hong Kong to Tokyo latency and RTT — 44.9 ms
Singapore to Tokyo latency and RTT — 68.9 ms
Seattle to Tokyo latency and RTT — 85 ms
Los Angeles to Tokyo latency and RTT — 101.2 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 118.6 ms
Moscow to Taipei latency and RTT — 132.1 ms
Marseille to Singapore latency and 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. 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 or browse more city-pair routes.

Moscow, Russia → Tokyo, Japan RTT