Marseille, France → Amsterdam, Netherlands RTT
ICMP RTT measurement results for Marseille, France, to Amsterdam, Netherlands: average latency, jitter, packet loss, and physical reference.
🇫🇷 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 |
| Destination Region | 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.
Ping series: MRS → AMS
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 20.3 ± 0.09 ms (SE)
Sample distribution: box = interquartile range (19.9–20.5 ms), median 20.1 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (9.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 19.74 |
| 2 | 100 | 20.08 |
| 3 | 200 | 19.84 |
| 4 | 300 | 20.40 |
| 5 | 400 | 20.43 |
| 6 | 500 | 20.33 |
| 7 | 600 | 19.89 |
| 8 | 700 | 19.97 |
| 9 | 800 | 19.95 |
| 10 | 900 | 20.59 |
| 11 | 1000 | 20.52 |
| 12 | 1100 | 20.08 |
| 13 | 1200 | 20.60 |
| 14 | 1300 | 20.37 |
| 15 | 1400 | 20.09 |
| 16 | 1500 | 20.37 |
| 17 | 1600 | 20.87 |
| 18 | 1700 | 20.19 |
| 19 | 1800 | 21.81 |
| 20 | 1900 | 21.75 |
| 21 | 2000 | 20.28 |
| 22 | 2100 | 21.89 |
| 23 | 2200 | 20.72 |
| 24 | 2300 | 20.65 |
| 25 | 2400 | 20.54 |
| 26 | 2500 | 20.06 |
| 27 | 2600 | 19.84 |
| 28 | 2700 | 20.96 |
| 29 | 2800 | 22.75 |
| 30 | 2900 | 20.88 |
| 31 | 3000 | 20.23 |
| 32 | 3100 | 19.75 |
| 33 | 3200 | 20.15 |
| 34 | 3300 | 19.81 |
| 35 | 3400 | 19.63 |
| 36 | 3500 | 19.95 |
| 37 | 3600 | 19.96 |
| 38 | 3700 | 20.07 |
| 39 | 3800 | 21.04 |
| 40 | 3900 | 20.03 |
| 41 | 4000 | 19.79 |
| 42 | 4100 | 19.92 |
| 43 | 4200 | 19.68 |
| 44 | 4300 | 19.94 |
| 45 | 4400 | 19.64 |
| 46 | 4500 | 19.97 |
| 47 | 4600 | 20.03 |
| 48 | 4700 | 19.66 |
| 49 | 4800 | 19.62 |
| 50 | 4900 | 19.69 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Marseille (43.29695, 5.38107) and Amsterdam (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 () | 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.
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% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 20.3 ms
- Minimum
- 20.1 ms
- Maximum
- 20.5 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Marseille (MRS)
- Destination PoP: Amsterdam (AMS)
- Region overview: Europe → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Amsterdam to Marseille latency and RTT — 19.6 ms
Fastest routes departing Marseille (MRS)
- Marseille to Paris latency and RTT — 8.9 ms
- Marseille to Frankfurt latency and RTT — 16 ms
- Marseille to London latency and RTT — 18.9 ms
- Marseille to Berlin latency and RTT — 20.6 ms
- Marseille to Moscow latency and RTT — 49.6 ms
Fastest routes arriving at Amsterdam (AMS)
- London to Amsterdam latency and RTT — 5.2 ms
- Frankfurt to Amsterdam latency and RTT — 5.9 ms
- Paris to Amsterdam latency and RTT — 7 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Moscow to Amsterdam latency and RTT — 37.6 ms
Same corridor (Europe → Europe)
- Amsterdam to London latency and RTT — 5.2 ms
- Amsterdam to Frankfurt latency and RTT — 5.9 ms
- Berlin to Frankfurt latency and 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. 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 or browse more city-pair routes.