Singapore → Moscow, Russia RTT
ICMP echo RTT from Singapore to Moscow, Russia: 147.6 ms average, 0% loss, 50 samples from the 2026-08-15T04:03:13Z round.
🇸🇬 Singapore (SIN) → 🇷🇺 Moscow, Russia (MOW)
Measurement round: 2026-08-15T04:03:13Z.
In the 2026-08-15T04:03:13Z round, ICMP echo RTT from Singapore to Moscow averaged 147.6 ms across 50 samples, with a minimum of 144.71 ms and a maximum of 154.68 ms. The standard deviation was just 2.32 ms with 1.95 ms jitter, and no packets were lost.
Although the geodesic distance is shorter at 8,423.2 km, the measured average is 1.79 times the straight-line fiber-floor value, translating to 55.9% fiber efficiency. The route therefore carries more extra latency than an ideal great-circle path, yet the very tight sample spread means that extra latency is stable.
This route was ranked 7th among the 19 outbound routes measured from Singapore in the same round. The set's median standard-deviation-to-average ratio was 3.08%, so this route's 2.32 ms standard deviation is notably tighter than the group norm.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 147.6 ms |
| Jitter | 1.95 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 82.49 ms |
| Fiber Efficiency | 55.9% |
| Latency Tier | Good |
| 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: SIN → MOW
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 147.6 ± 0.33 ms (SE)
Sample distribution: box = interquartile range (145.9–148.8 ms), median 147.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 (82.5 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 145.50 |
| 2 | 100 | 145.10 |
| 3 | 200 | 145.13 |
| 4 | 300 | 145.92 |
| 5 | 400 | 145.32 |
| 6 | 500 | 146.25 |
| 7 | 600 | 146.95 |
| 8 | 700 | 145.22 |
| 9 | 800 | 145.01 |
| 10 | 900 | 145.09 |
| 11 | 1000 | 147.62 |
| 12 | 1100 | 145.98 |
| 13 | 1200 | 145.12 |
| 14 | 1300 | 144.71 |
| 15 | 1400 | 144.99 |
| 16 | 1500 | 147.02 |
| 17 | 1600 | 146.17 |
| 18 | 1700 | 154.68 |
| 19 | 1800 | 151.31 |
| 20 | 1900 | 148.66 |
| 21 | 2000 | 149.95 |
| 22 | 2100 | 147.28 |
| 23 | 2200 | 145.99 |
| 24 | 2300 | 149.09 |
| 25 | 2400 | 152.09 |
| 26 | 2500 | 147.65 |
| 27 | 2600 | 146.97 |
| 28 | 2700 | 153.91 |
| 29 | 2800 | 147.67 |
| 30 | 2900 | 148.82 |
| 31 | 3000 | 150.33 |
| 32 | 3100 | 146.93 |
| 33 | 3200 | 146.98 |
| 34 | 3300 | 145.45 |
| 35 | 3400 | 148.01 |
| 36 | 3500 | 146.49 |
| 37 | 3600 | 151.52 |
| 38 | 3700 | 146.80 |
| 39 | 3800 | 147.10 |
| 40 | 3900 | 146.64 |
| 41 | 4000 | 145.51 |
| 42 | 4100 | 147.85 |
| 43 | 4200 | 150.92 |
| 44 | 4300 | 148.21 |
| 45 | 4400 | 150.07 |
| 46 | 4500 | 149.13 |
| 47 | 4600 | 148.98 |
| 48 | 4700 | 147.79 |
| 49 | 4800 | 147.81 |
| 50 | 4900 | 146.31 |
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.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Singapore (1.28967, 103.85007) and Moscow (55.75204, 37.61781). 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 () | 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-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 144.71 ms |
| Average RTT | 147.6 ms |
| Maximum RTT | 154.68 ms |
| Standard deviation | 2.32 ms |
| Stdev / average | 1.6% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 147.4 ms
- Minimum
- 146.4 ms
- Maximum
- 149.0 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Singapore (SIN)
- Destination PoP: Moscow (MOW)
- Region overview: Asia Pacific → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Moscow to Singapore latency and RTT — 148.3 ms
Fastest routes departing Singapore (SIN)
- Singapore to Hong Kong latency and RTT — 30.9 ms
- Singapore to Taipei latency and RTT — 44.3 ms
- Singapore to Tokyo latency and RTT — 69.6 ms
- Singapore to Melbourne latency and RTT — 87.8 ms
- Singapore to Sydney latency and RTT — 95.3 ms
Fastest routes arriving at Moscow (MOW)
- Berlin to Moscow latency and RTT — 28 ms
- Frankfurt to Moscow latency and RTT — 34.8 ms
- Amsterdam to Moscow latency and RTT — 38.2 ms
- London to Moscow latency and RTT — 44.1 ms
- Paris to Moscow latency and RTT — 44.5 ms
Same corridor (Asia Pacific → Europe)
- Hong Kong to Moscow latency and RTT — 116.6 ms
- Taipei to Moscow latency and RTT — 131.7 ms
- Singapore to Marseille latency and RTT — 138.8 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/sin-mow.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → Moscow 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.