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

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

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

During the 2026-08-16T04:07:28Z measurement round, 50 ICMP echo probes from Moscow to Taipei produced an average RTT of 132.1 ms, with a minimum of 126.75 ms and a maximum of 145.67 ms. No packets were lost, and jitter was 4.42 ms.

Over a geodesic distance of 7,369 km, the theoretical vacuum one-way floor is 49.16 ms and the fiber floor is 72.16 ms. The observed average is 1.83 times the fiber floor, placing the route at 54.6% fiber-floor efficiency.

Ranked 10th among the 19 routes measured in the same round, Moscow-to-Taipei sits around the middle of the set. Its standard deviation of 4.52 ms is about 3.4% of the average, just above the 3.28% median standard-deviation-to-average ratio for the round. With zero packet loss and moderate jitter, this round offers a stable baseline for Moscow-to-Taipei latency.

Latency Summary

Metric	Value
RTT	132.1 ms
Jitter	4.42 ms
Packet Loss	0%
Standard Fiber Floor	72.16 ms
Fiber Efficiency	54.6%
Latency Tier	Good
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 → TPE

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

Sample distribution: box = interquartile range (128.7–134.2 ms), median 131.3 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 (72.2 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	137.23
2	100	139.08
3	200	131.26
4	300	135.26
5	400	141.39
6	500	131.63
7	600	129.27
8	700	139.00
9	800	131.29
10	900	128.18
11	1000	127.32
12	1100	129.17
13	1200	127.59
14	1300	128.17
15	1400	131.46
16	1500	132.47
17	1600	137.52
18	1700	130.30
19	1800	128.52
20	1900	127.19
21	2000	129.36
22	2100	135.37
23	2200	133.59
24	2300	130.06
25	2400	127.64
26	2500	132.02
27	2600	129.66
28	2700	127.40
29	2800	127.44
30	2900	126.75
31	3000	127.18
32	3100	126.79
33	3200	142.31
34	3300	131.93
35	3400	129.10
36	3500	141.84
37	3600	133.95
38	3700	132.53
39	3800	131.81
40	3900	145.67
41	4000	134.39
42	4100	129.49
43	4200	134.26
44	4300	133.10
45	4400	129.94
46	4500	136.55
47	4600	129.84
48	4700	133.58
49	4800	130.01
50	4900	128.14

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 Taipei (25.05306, 121.52639). 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.83×

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	126.75 ms
Average RTT	132.1 ms
Maximum RTT	145.67 ms
Standard deviation	4.52 ms
Stdev / average	3.4%

RTT trend

Estimated route stability across the selected time window.

Average: 132.2 ms
Minimum: 131.3 ms
Maximum: 133.5 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Taipei to Moscow latency and RTT — 132.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 Taipei (TPE)

Hong Kong to Taipei latency and RTT — 14.7 ms
Tokyo to Taipei latency and RTT — 32.3 ms
Singapore to Taipei latency and RTT — 45.8 ms
Seattle to Taipei latency and RTT — 114.7 ms
Sydney to Taipei latency and RTT — 131.7 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 118.6 ms
Marseille to Singapore latency and RTT — 139.6 ms
Berlin to Hong Kong latency and RTT — 144.9 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-tpe.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Taipei 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 → Taipei, Taiwan RTT