# Marseille, France → Amsterdam, Netherlands RTT

🇫🇷 **Marseille, France (MRS)** → 🇳🇱 **Amsterdam, Netherlands (AMS)**

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

ICMP echo measurements in the 2026-08-16T04:07:28Z round put Marseille-to-Amsterdam at an average RTT of 20.3 ms, with a minimum of 19.62 ms and a maximum of 22.75 ms over 50 samples. The route posted zero packet loss and 0.48 ms of jitter, which is why it lands in the 'Ultra-Low' latency tier.

The geodesic distance is about 1,009.9 km, placing the vacuum floor at 6.74 ms and the fiber floor at 9.89 ms. At 20.3 ms, the measured RTT is 2.05 times the fiber floor, or roughly 48.7% fiber efficiency, leaving room for the extra cable length that real networks require between a Mediterranean landing hub and a Northwest European interconnection point.

This route ranked 4th among the 19 outbound routes measured from Marseille in this round, placing it close to the top of the source's latency order. Its standard deviation of 0.64 ms is about 3.15% of the average, slightly below the round-wide median variability of 3.28% across the outbound group.

The practical takeaway is that the Marseille–Amsterdam path is both fast and consistent for a roughly 1,000 km link. With no sample loss and very low jitter, the 20.3 ms average is a representative value rather than a lucky outlier.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **20.3 ms**                                    |
| Jitter               | **0.48 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **9.89 ms**                                    |
| Fiber Efficiency     | **48.7%**                                      |
| Latency Tier         | Ultra-Low                                      |
| Source Region        | [Europe](/docs/network/latency/regions/europe) |
| 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 [Marseille](https://www.geonames.org/2995469) (43.29695, 5.38107) and [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **1,009.9 km** |
| Vacuum RTT floor                              | **6.74 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **9.89 ms**    |
| Low-latency fiber material floor              | **9.85 ms**    |
| Engineering floor (5% path allowance)         | **10.39 ms**   |
| Research 1.33× mapped-fiber reference         | **13.15 ms**   |
| Estimated unamplified path loss               | **212.1 dB**   |
| Transparent optical spans / inline amplifiers | **14 / 13**    |
| Published RTT inflation over fiber floor      | **2.05×**      |

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        | **19.62 ms** |
| Average RTT        | **20.3 ms**  |
| Maximum RTT        | **22.75 ms** |
| Standard deviation | **0.64 ms**  |
| Stdev / average    | **3.2%**     |

## Route Context

* Departure PoP: [Marseille (MRS)](/docs/network/latency/mrs-marseille)
* Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [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**

* [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 ms

**Fastest routes departing Marseille (MRS)**

* [Marseille to Paris latency and RTT](/docs/network/latency/pairs/mrs-par-rtt) — 8.9 ms
* [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms
* [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 ms
* [Marseille to Moscow latency and RTT](/docs/network/latency/pairs/mrs-mow-rtt) — 49.6 ms

**Fastest routes arriving at Amsterdam (AMS)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms
* [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Moscow to Amsterdam latency and RTT](/docs/network/latency/pairs/mow-ams-rtt) — 37.6 ms

**Same corridor (Europe → Europe)**

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