Hats Network | LogoHats Network
NetworkLatencyPairs

Tokyo to Moscow Latency, Ping & RTT | AS203314

Tokyo to Moscow ping and RTT: 165.3 ms, 1.75 ms jitter, 73.42 ms fiber floor, and 44.4% efficiency across AS203314. Updated 2026-07-19.

πŸ‡―πŸ‡΅ This page compares the published ping and round-trip time (RTT) from Tokyo (TYO) to πŸ‡·πŸ‡Ί Moscow (MOW) with vacuum and optical-fiber physical limits.

Latency Summary

MetricValue
RTT165.3 ms
Jitter1.75 ms
Packet Loss0.08%
Standard Fiber Floor73.42 ms
Fiber Efficiency44.4%
Latency TierFair
Source RegionAsia Pacific
Destination RegionEurope

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 ReferenceValue
WGS-84 geodesic distance7,497 km
Vacuum RTT floor50.01 ms
Standard fiber RTT floor (ng=1.4679n_g=1.4679)73.42 ms
Low-latency fiber material floor73.12 ms
Engineering floor (5% path allowance)77.1 ms
Research 1.33Γ— mapped-fiber reference97.64 ms
Estimated unamplified path loss1574.4 dB
Transparent optical spans / inline amplifiers99 / 98
Published RTT inflation over fiber floor2.25Γ—

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 following estimated indicators summarize route stability for the current publication period and are intended for comparative planning rather than SLA evaluation.

Stability IndicatorValue
Minimum RTT163.1 ms
Median RTT (p50)165.1 ms
95th percentile RTT (p95)168.1 ms
Maximum RTT169 ms
Jitter1.75 ms
Packet loss0.08%

RTT trend

Estimated route stability across the selected time window.

Average
165.1 ms
Minimum
163.8 ms
Maximum
166.4 ms
Average loss
0.01%

Route Context

About This Measurement

Published RTT reflects best-case backbone path behavior. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. Stability indicators are comparative estimates, and none of these values is an SLA.


Data auto-generated on July 19, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

On this page