# Melbourne, Australia → Marseille, France RTT

🇦🇺 **Melbourne, Australia (MEL)** → 🇫🇷 **Marseille, France (MRS)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo requests from Melbourne, Australia to Marseille, France returned an average round-trip time of 233.5 ms over 50 probes, with a low of 221.74 ms and a high of 271.93 ms. The route lost no packets and earned a Fair latency classification.

Against a straight-line fiber path, this average is 1.44 times the theoretical fiber floor of roughly 162 ms, placing the route at 69.5 percent fiber efficiency over a geodesic distance of 16,579.2 km. That gap is a useful distance-adjusted sign of how intercontinental transport overhead accumulates.

This route ranked 11th among the 19 route pairs measured in the same round. Its standard deviation of 10.3 ms is about 4.4 percent of the average RTT, somewhat above the route-set median of 3.28 percent, while jitter averaged 8.57 ms.

Given Marseille's role as a Mediterranean cable landing hub, this measurement offers a useful Melbourne-to-southern-Europe reference point for steady, loss-free ICMP reachability.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **233.5 ms**                                               |
| Jitter               | **8.57 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **162.36 ms**                                              |
| Fiber Efficiency     | **69.5%**                                                  |
| 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 [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **16,579.2 km** |
| Vacuum RTT floor                              | **110.6 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **162.36 ms**   |
| Low-latency fiber material floor              | **161.7 ms**    |
| Engineering floor (5% path allowance)         | **170.5 ms**    |
| Research 1.33× mapped-fiber reference         | **215.93 ms**   |
| Estimated unamplified path loss               | **3481.6 dB**   |
| Transparent optical spans / inline amplifiers | **218 / 217**   |
| Published RTT inflation over fiber floor      | **1.44×**       |

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        | **221.74 ms** |
| Average RTT        | **233.5 ms**  |
| Maximum RTT        | **271.93 ms** |
| Standard deviation | **10.3 ms**   |
| Stdev / average    | **4.4%**      |

## Route Context

* Departure PoP: [Melbourne (MEL)](/docs/network/latency/mel-melbourne)
* Destination PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille)
* 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**

* [Marseille to Melbourne latency and RTT](/docs/network/latency/pairs/mrs-mel-rtt) — 234.2 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 Marseille (MRS)**

* [Paris to Marseille latency and RTT](/docs/network/latency/pairs/par-mrs-rtt) — 8.9 ms
* [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms
* [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 ms
* [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms
* [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 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-mrs.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Melbourne → Marseille 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-mrs-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.