Moscow, Russia to Singapore, Singapore ICMP RTT measurement: average 147.3 ms, jitter, packet loss, and latency details.

🇷🇺 Moscow, Russia (MOW) → 🇸🇬 Singapore (SIN)

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

During the 2026-08-16T04:07:28Z round, Moscow to Singapore returned an average ICMP echo RTT of 147.3 ms, a minimum of 144.41 ms, a maximum of 156.92 ms, and no packet loss across 50 samples.

At 1.79 times the fiber-optic propagation floor for the 8,423 km great-circle distance, the average corresponds to 56% fiber efficiency. The 2.32 ms standard deviation and 1.99 ms jitter are both small, indicating a highly consistent route.

This path was ranked 12th among the 19 Moscow outbound paths in this round, close to the middle of the group. Its relative variability is about 1.6% of the average, well below the 3.28% median for those 19 paths, so mid-pack latency arrives with unusually steady timing.

Latency Summary

Metric	Value
RTT	147.3 ms
Jitter	1.99 ms
Packet Loss	0%
Standard Fiber Floor	82.49 ms
Fiber Efficiency	56%
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 → SIN

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

Sample distribution: box = interquartile range (145.7–148.2 ms), median 146.8 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 (82.5 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	145.24
2	100	145.84
3	200	148.26
4	300	146.07
5	400	148.88
6	500	147.24
7	600	147.21
8	700	147.96
9	800	147.46
10	900	146.81
11	1000	156.92
12	1100	149.69
13	1200	146.09
14	1300	145.20
15	1400	146.30
16	1500	149.57
17	1600	147.45
18	1700	145.73
19	1800	147.91
20	1900	146.84
21	2000	153.72
22	2100	149.10
23	2200	148.20
24	2300	145.62
25	2400	146.13
26	2500	144.88
27	2600	145.94
28	2700	145.38
29	2800	147.00
30	2900	148.10
31	3000	145.72
32	3100	145.05
33	3200	145.58
34	3300	148.65
35	3400	148.39
36	3500	146.32
37	3600	149.49
38	3700	147.09
39	3800	146.83
40	3900	147.69
41	4000	145.86
42	4100	145.78
43	4200	146.15
44	4300	145.56
45	4400	144.77
46	4500	144.41
47	4600	144.64
48	4700	149.81
49	4800	152.24
50	4900	148.23

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 Singapore (1.28967, 103.85007). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,423.2 km
Vacuum RTT floor	56.19 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	82.49 ms
Low-latency fiber material floor	82.15 ms
Engineering floor (5% path allowance)	86.62 ms
Research 1.33× mapped-fiber reference	109.71 ms
Estimated unamplified path loss	1768.9 dB
Transparent optical spans / inline amplifiers	111 / 110
Published RTT inflation over fiber floor	1.79×

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	144.41 ms
Average RTT	147.3 ms
Maximum RTT	156.92 ms
Standard deviation	2.32 ms
Stdev / average	1.6%

RTT trend

Estimated route stability across the selected time window.

Average: 147.6 ms
Minimum: 146.6 ms
Maximum: 148.7 ms
Average loss: 0.02%

Route Context

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

Reverse direction

Singapore to Moscow latency and RTT — 147.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 Singapore (SIN)

Hong Kong to Singapore latency and RTT — 31.5 ms
Taipei to Singapore latency and RTT — 44.3 ms
Tokyo to Singapore latency and RTT — 69.4 ms
Melbourne to Singapore latency and RTT — 88.4 ms
Sydney to Singapore latency and RTT — 94.5 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-sin.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Moscow → Singapore 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 → Singapore RTT