Tokyo to Moscow RTT measurements: ICMP echo round-trip latency between Tokyo, Japan and Moscow, Russia, including jitter and packet loss.

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

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

ICMP echo probes from Tokyo to Moscow in the 2026-08-16T04:07:28Z round recorded an average round-trip time of 161.7 ms across 50 samples, with a minimum of 155.32 ms and a maximum of 174.84 ms. Zero packets were lost, and jitter was 4.87 ms.

The great-circle distance is about 7,497 km, so the vacuum floor is 50.01 ms and the direct-fiber floor is 73.42 ms. At 161.7 ms the measured average is 2.2 times the fiber floor, equivalent to about 45.4% fiber efficiency; the route's absolute latency is low, but its distance-adjusted efficiency trails that ideal.

Among the 19 outbound routes from this origin, the path ranked 11th, placing it near the middle rather than the top. Its standard deviation of 4.83 ms is about 3.0% of the average, below the 3.28% midpoint across the set, so the path combines moderate rank with good consistency and no loss.

Latency Summary

Metric	Value
RTT	161.7 ms
Jitter	4.87 ms
Packet Loss	0%
Standard Fiber Floor	73.42 ms
Fiber Efficiency	45.4%
Latency Tier	Fair
Source Region	Asia Pacific
Destination Region	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.

Ping series: TYO → MOW

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

Sample distribution: box = interquartile range (158.1–164.4 ms), median 160.0 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	155.32
2	100	158.24
3	200	159.34
4	300	158.93
5	400	157.77
6	500	163.64
7	600	159.71
8	700	168.03
9	800	164.20
10	900	167.37
11	1000	161.64
12	1100	158.77
13	1200	170.31
14	1300	164.91
15	1400	158.68
16	1500	156.58
17	1600	157.25
18	1700	164.70
19	1800	174.84
20	1900	167.03
21	2000	161.61
22	2100	172.75
23	2200	162.19
24	2300	158.44
25	2400	163.55
26	2500	159.13
27	2600	157.06
28	2700	166.43
29	2800	159.81
30	2900	163.24
31	3000	158.01
32	3100	163.22
33	3200	161.66
34	3300	157.48
35	3400	157.53
36	3500	156.04
37	3600	160.25
38	3700	158.32
39	3800	174.73
40	3900	164.47
41	4000	158.65
42	4100	156.59
43	4200	155.69
44	4300	157.72
45	4400	161.95
46	4500	168.57
47	4600	165.40
48	4700	159.49
49	4800	157.43
50	4900	160.33

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 Tokyo (35.68950, 139.69171) and Moscow (55.75204, 37.61781). 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.2×

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	155.32 ms
Average RTT	161.7 ms
Maximum RTT	174.84 ms
Standard deviation	4.83 ms
Stdev / average	3.0%

RTT trend

Estimated route stability across the selected time window.

Average: 161.6 ms
Minimum: 160.5 ms
Maximum: 163.1 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Moscow to Tokyo latency and RTT — 162.2 ms

Fastest routes departing Tokyo (TYO)

Tokyo to Taipei latency and RTT — 32.3 ms
Tokyo to Hong Kong latency and RTT — 44.8 ms
Tokyo to Singapore latency and RTT — 69.4 ms
Tokyo to Seattle latency and RTT — 84.8 ms
Tokyo to Los Angeles latency and RTT — 101.2 ms

Fastest routes arriving at Moscow (MOW)

Berlin to Moscow latency and RTT — 28.6 ms
Frankfurt to Moscow latency and RTT — 34.7 ms
Amsterdam to Moscow latency and RTT — 38.1 ms
London to Moscow latency and RTT — 43.5 ms
Paris to Moscow latency and RTT — 44.7 ms

Same corridor (Asia Pacific → Europe)

Hong Kong to Moscow latency and RTT — 118.2 ms
Taipei to Moscow latency and RTT — 132.7 ms
Singapore to Marseille latency and RTT — 140.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/tyo-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Moscow 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.

Tokyo, Japan → Moscow, Russia RTT