# Miami, USA → Amsterdam, Netherlands RTT

🇺🇸 **Miami, USA (MIA)** → 🇳🇱 **Amsterdam, Netherlands (AMS)**

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

For the 2026-08-16T04:07:28Z measurement round, Miami to Amsterdam returned an average ICMP RTT of 106 ms from 50 samples, with a minimum of 103.48 ms and a maximum of 113.5 ms. No packets were lost, and jitter held at 1.97 ms, so the route operated in the good latency tier throughout the test.

The 7,457.8 km geodesic path has a vacuum-floor latency of 49.75 ms and a realistic fiber floor of 73.03 ms. At 106 ms average, the observed RTT is about 1.45 times that fiber floor, an efficiency of 68.9%, meaning the path covers the distance reasonably but with expected transatlantic network overhead.

The route ranked 6th among the 19 outbound routes measured from Miami, placing it in the faster half. Its standard deviation of 2.2 ms equals about 2.1% of the average, below the network-wide median standard-deviation-to-average ratio of 3.28%, so the path displayed better-than-typical consistency as well.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **106 ms**                                                   |
| Jitter               | **1.97 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **73.03 ms**                                                 |
| Fiber Efficiency     | **68.9%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| 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 [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) 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                      | **7,457.8 km** |
| Vacuum RTT floor                              | **49.75 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **73.03 ms**   |
| Low-latency fiber material floor              | **72.74 ms**   |
| Engineering floor (5% path allowance)         | **76.69 ms**   |
| Research 1.33× mapped-fiber reference         | **97.13 ms**   |
| Estimated unamplified path loss               | **1566.1 dB**  |
| Transparent optical spans / inline amplifiers | **98 / 97**    |
| Published RTT inflation over fiber floor      | **1.45×**      |

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        | **103.48 ms** |
| Average RTT        | **106 ms**    |
| Maximum RTT        | **113.5 ms**  |
| Standard deviation | **2.2 ms**    |
| Stdev / average    | **2.1%**      |

## Route Context

* Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Destination PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [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 Miami latency and RTT](/docs/network/latency/pairs/ams-mia-rtt) — 106 ms

**Fastest routes departing Miami (MIA)**

* [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms
* [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 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
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms

**Same corridor (North America → Europe)**

* [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms
* [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms
* [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.9 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/mia-ams.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → 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/mia-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.