# Sydney, Australia → Moscow, Russia RTT

🇦🇺 **Sydney, Australia (SYD)** → 🇷🇺 **Moscow, Russia (MOW)**

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

ICMP echo measurements collected at 2026-08-16T04:07:28Z put the Sydney–Moscow round-trip time at 242.2 ms on average, based on 50 probes sent at 100 ms intervals. The minimum RTT was 230.07 ms, the maximum was 270.93 ms, and packet loss was zero.

The route's short-term stability is contained for the distance: standard deviation was 9.04 ms and jitter 7.98 ms, or roughly 3.7% and 3.3% of the average. This Sydney–Moscow path ranks 12th by average RTT among the 19 outgoing paths measured in the same round, with variability just above the 3.28% median ratio for those paths.

The great-circle distance from Sydney to Moscow is about 14,483.9 km, and a direct fiber path at the speed of light in glass would need about 141.84 ms. The observed 242.2 ms is therefore 1.71 times that floor, with a fiber-efficiency score of 58.6% — a reminder that the effective path is considerably longer than the geodesic line, even though no probes were lost and the jitter band stayed narrow.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **242.2 ms**                                               |
| Jitter               | **7.98 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **141.84 ms**                                              |
| Fiber Efficiency     | **58.6%**                                                  |
| Latency Tier         | Fair                                                       |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Europe](/docs/network/latency/regions/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.

## 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 [Sydney](https://www.geonames.org/2147714) (-33.86785, 151.20732) and [Moscow](https://www.geonames.org/524901) (55.75204, 37.61781). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **14,483.9 km** |
| Vacuum RTT floor                              | **96.63 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **141.84 ms**   |
| Low-latency fiber material floor              | **141.27 ms**   |
| Engineering floor (5% path allowance)         | **148.95 ms**   |
| Research 1.33× mapped-fiber reference         | **188.64 ms**   |
| Estimated unamplified path loss               | **3041.6 dB**   |
| Transparent optical spans / inline amplifiers | **191 / 190**   |
| Published RTT inflation over fiber floor      | **1.71×**       |

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        | **230.07 ms** |
| Average RTT        | **242.2 ms**  |
| Maximum RTT        | **270.93 ms** |
| Standard deviation | **9.04 ms**   |
| Stdev / average    | **3.7%**      |

## Route Context

* Departure PoP: [Sydney (SYD)](/docs/network/latency/syd-sydney)
* Destination PoP: [Moscow (MOW)](/docs/network/latency/mow-moscow)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe)
* 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**

* [Moscow to Sydney latency and RTT](/docs/network/latency/pairs/mow-syd-rtt) — 241.8 ms

**Fastest routes departing Sydney (SYD)**

* [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms
* [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms
* [Sydney to Tokyo latency and RTT](/docs/network/latency/pairs/syd-tyo-rtt) — 101.3 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms
* [Sydney to Hong Kong latency and RTT](/docs/network/latency/pairs/syd-hkg-rtt) — 135.7 ms

**Fastest routes arriving at Moscow (MOW)**

* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms
* [Amsterdam to Moscow latency and RTT](/docs/network/latency/pairs/ams-mow-rtt) — 38.1 ms
* [London to Moscow latency and RTT](/docs/network/latency/pairs/lon-mow-rtt) — 43.5 ms
* [Paris to Moscow latency and RTT](/docs/network/latency/pairs/par-mow-rtt) — 44.7 ms

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

* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms
* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms
* [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.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/syd-mow.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Sydney → Moscow 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/syd-mow-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.