# Moscow, Russia → Singapore RTT

🇷🇺 **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](/docs/network/latency/regions/europe)             |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781) and [Singapore](https://www.geonames.org/1880252) (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](/docs/network/latency/theoretical-fiber-latency).

## 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%**      |

## Route Context

* Departure PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Singapore to Moscow latency and RTT](/docs/network/latency/pairs/sin-mow-rtt) — 147.7 ms

**Fastest routes departing Moscow (MOW)**

* [Moscow to Berlin latency and RTT](/docs/network/latency/pairs/mow-ber-rtt) — 27.5 ms
* [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms
* [Moscow to London latency and RTT](/docs/network/latency/pairs/mow-lon-rtt) — 42.4 ms
* [Moscow to Paris latency and RTT](/docs/network/latency/pairs/mow-par-rtt) — 44 ms

**Fastest routes arriving at Singapore (SIN)**

* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms
* [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms
* [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms

**Same corridor (Europe → Asia Pacific)**

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-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](/opendata/latency/). 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](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/mow-sin-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.