# Melbourne, Australia → Moscow, Russia RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇷🇺 **Moscow, Russia (MOW)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Melbourne, Australia to Moscow, Russia produced an average round-trip time of 236.1 ms across 50 probes, with a minimum of 226.33 ms and a maximum of 266.71 ms. Packet loss was zero and the latency tier was Fair.

The measured average is 1.67 times the theoretical fiber floor of about 141.13 ms, yielding 59.8 percent fiber efficiency over a geodesic distance of 14,412.1 km. The larger inflation suggests that this route carries more distance-adjusted overhead than its raw geographic length alone would imply.

Ranked 12th among the 19 route pairs in this measurement set, the route showed a standard deviation of 8.22 ms—about 3.5 percent of the average RTT—close to the route-set median of 3.28 percent. Jitter averaged 7.04 ms, and the spread between minimum and maximum RTT stayed under 41 ms.

Moscow's position as a transit corridor between European and Asia-Pacific networks makes this a useful reference for east-west intercontinental round-trip behavior from Melbourne.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **236.1 ms**                                               |
| Jitter               | **7.04 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **141.13 ms**                                              |
| Fiber Efficiency     | **59.8%**                                                  |
| 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 [Melbourne](https://www.geonames.org/2158177) (-37.81400, 144.96332) 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,412.1 km** |
| Vacuum RTT floor                              | **96.15 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **141.13 ms**   |
| Low-latency fiber material floor              | **140.57 ms**   |
| Engineering floor (5% path allowance)         | **148.21 ms**   |
| Research 1.33× mapped-fiber reference         | **187.71 ms**   |
| Estimated unamplified path loss               | **3026.5 dB**   |
| Transparent optical spans / inline amplifiers | **190 / 189**   |
| Published RTT inflation over fiber floor      | **1.67×**       |

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        | **226.33 ms** |
| Average RTT        | **236.1 ms**  |
| Maximum RTT        | **266.71 ms** |
| Standard deviation | **8.22 ms**   |
| Stdev / average    | **3.5%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* 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 Melbourne latency and RTT](/docs/network/latency/pairs/mow-mel-rtt) — 235.9 ms

**Fastest routes departing Melbourne (MEL)**

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