ICMP echo RTT data from the 2026-08-15 round for Moscow (Russia) to Singapore (Singapore): average, min, max, jitter, packet loss.

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

Measurement round: 2026-08-15T04:03:13Z.

On the 2026-08-15T04:03:13Z ICMP echo round, Moscow to Singapore produced an average RTT of 148.3 ms across 50 samples at a 100 ms interval. The minimum was 140.36 ms, the maximum 174.06 ms, the standard deviation 7.03 ms, and jitter 6.14 ms; no probes were lost.

Because Singapore is about 8,423.2 km from Moscow along a great-circle path, a vacuum signal would need 56.19 ms and a straight fiber path 82.49 ms. At 148.3 ms, the route runs 1.8x above the fiber floor, placing fiber efficiency at 55.6% and the latency tier at Good.

Among the 19 Moscow outbound routes in this round, the route ranked 12th; its RTT variability was roughly 4.7% of the average, above the round's median variability ratio of 3.08%. Even so, the consistent 148 ms average, low jitter, and zero packet loss make this a stable ICMP result for the Moscow-Singapore path.

Latency Summary

Metric	Value
RTT	148.3 ms
Jitter	6.14 ms
Packet Loss	0%
Standard Fiber Floor	82.49 ms
Fiber Efficiency	55.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 → SIN

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 148.3 ± 0.99 ms (SE)

Sample distribution: box = interquartile range (143.5–151.5 ms), median 146.4 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	154.02
2	100	146.61
3	200	145.53
4	300	143.02
5	400	141.01
6	500	141.69
7	600	140.60
8	700	141.20
9	800	140.46
10	900	142.26
11	1000	142.77
12	1100	141.46
13	1200	140.36
14	1300	159.67
15	1400	149.07
16	1500	145.56
17	1600	144.53
18	1700	148.08
19	1800	149.91
20	1900	153.76
21	2000	146.77
22	2100	143.35
23	2200	145.83
24	2300	143.85
25	2400	150.01
26	2500	143.36
27	2600	152.41
28	2700	152.43
29	2800	149.72
30	2900	144.28
31	3000	141.72
32	3100	158.58
33	3200	151.75
34	3300	146.68
35	3400	145.57
36	3500	166.57
37	3600	149.25
38	3700	145.55
39	3800	174.06
40	3900	153.47
41	4000	151.62
42	4100	144.60
43	4200	144.20
44	4300	151.98
45	4400	148.19
46	4500	144.63
47	4600	167.10
48	4700	150.99
49	4800	148.76
50	4900	146.15

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.8×

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-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	140.36 ms
Average RTT	148.3 ms
Maximum RTT	174.06 ms
Standard deviation	7.03 ms
Stdev / average	4.7%

RTT trend

Estimated route stability across the selected time window.

Average: 148.4 ms
Minimum: 147.4 ms
Maximum: 149.4 ms
Average loss: 0.01%

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.6 ms

Fastest routes departing Moscow (MOW)

Moscow to Berlin latency and RTT — 27 ms
Moscow to Frankfurt latency and RTT — 35 ms
Moscow to Amsterdam latency and RTT — 39.3 ms
Moscow to London latency and RTT — 42.4 ms
Moscow to Paris latency and RTT — 43.9 ms

Fastest routes arriving at Singapore (SIN)

Hong Kong to Singapore latency and RTT — 31.2 ms
Taipei to Singapore latency and RTT — 44.2 ms
Tokyo to Singapore latency and RTT — 69.6 ms
Melbourne to Singapore latency and RTT — 88.3 ms
Sydney to Singapore latency and RTT — 94.7 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 118.5 ms
Moscow to Taipei latency and RTT — 130.9 ms
Marseille to Singapore latency and RTT — 138.5 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-15T04:03:13Z, CC BY 4.0".

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

Moscow, Russia → Singapore RTT