# Miami, USA → New York, USA RTT

🇺🇸 **Miami, USA (MIA)** → 🇺🇸 **New York, USA (NYC)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo requests from Miami to New York averaged 33.3 ms, with a minimum of 31.68 ms, a maximum of 39.04 ms, and zero packet loss across 50 samples.

The observed average is 1.94 times the straight-line fiber floor of 17.17 ms over the 1,753.2 km geodesic distance, or 51.6% straight-line fiber efficiency, so the route stays reasonably close to the physical latency limit.

Ranked second among the 19 routes measured in the same round, this path sits in an Excellent tier; the median standard-deviation-to-average ratio across that route set was 3.28%, while its own 1.51 ms standard deviation and 1.24 ms jitter keep the absolute spread compact.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **33.3 ms**                                                  |
| Jitter               | **1.24 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **17.17 ms**                                                 |
| Fiber Efficiency     | **51.6%**                                                    |
| Latency Tier         | Excellent                                                    |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| Destination Region   | [North America](/docs/network/latency/regions/north-america) |

## 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **1,753.2 km** |
| Vacuum RTT floor                              | **11.7 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **17.17 ms**   |
| Low-latency fiber material floor              | **17.1 ms**    |
| Engineering floor (5% path allowance)         | **18.03 ms**   |
| Research 1.33× mapped-fiber reference         | **22.83 ms**   |
| Estimated unamplified path loss               | **368.2 dB**   |
| Transparent optical spans / inline amplifiers | **24 / 23**    |
| Published RTT inflation over fiber floor      | **1.94×**      |

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        | **31.68 ms** |
| Average RTT        | **33.3 ms**  |
| Maximum RTT        | **39.04 ms** |
| Standard deviation | **1.51 ms**  |
| Stdev / average    | **4.5%**     |

## Route Context

* Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [North America](/docs/network/latency/regions/north-america)
* 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**

* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms

**Fastest routes departing Miami (MIA)**

* [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.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
* [Miami to Amsterdam latency and RTT](/docs/network/latency/pairs/mia-ams-rtt) — 106 ms

**Fastest routes arriving at New York (NYC)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms
* [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms

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

* [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms
* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.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-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → New York 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-nyc-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.