# Seattle, USA → Miami, USA RTT

🇺🇸 **Seattle, USA (SEA)** → 🇺🇸 **Miami, USA (MIA)**

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

For round 2026-08-16T04:07:28Z, the ICMP echo path from Seattle, USA to Miami, USA averaged 81.7 ms round-trip time, with 50 samples spanning 79.89 ms to 89.57 ms and no packet loss.

That average sits about 1.9 times above the fiber-floor estimate for the 4,399.4 km span, and the route's 52.7 percent fiber efficiency places it in the Good latency tier. Jitter remains moderate at 1.22 ms, while the 1.94 ms standard deviation shows most samples cluster tightly around the average.

This route ranks fourth among the 19 outbound routes in its measurement set. Its standard-deviation-to-average ratio of about 2.4 percent is below the set-wide median of 3.28 percent, and the zero-loss result with low jitter means the distance overhead does not translate into erratic echo responses.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **81.7 ms**                                                  |
| Jitter               | **1.22 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **43.08 ms**                                                 |
| Fiber Efficiency     | **52.7%**                                                    |
| Latency Tier         | Good                                                         |
| 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 [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207) and [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **4,399.4 km** |
| Vacuum RTT floor                              | **29.35 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **43.08 ms**   |
| Low-latency fiber material floor              | **42.91 ms**   |
| Engineering floor (5% path allowance)         | **45.24 ms**   |
| Research 1.33× mapped-fiber reference         | **57.3 ms**    |
| Estimated unamplified path loss               | **923.9 dB**   |
| Transparent optical spans / inline amplifiers | **58 / 57**    |
| Published RTT inflation over fiber floor      | **1.9×**       |

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        | **79.89 ms** |
| Average RTT        | **81.7 ms**  |
| Maximum RTT        | **89.57 ms** |
| Standard deviation | **1.94 ms**  |
| Stdev / average    | **2.4%**     |

## Route Context

* Departure PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* 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**

* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms

**Fastest routes departing Seattle (SEA)**

* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [Seattle to Ashburn latency and RTT](/docs/network/latency/pairs/sea-iad-rtt) — 61.5 ms
* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms

**Fastest routes arriving at Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms
* [London to Miami latency and RTT](/docs/network/latency/pairs/lon-mia-rtt) — 101.9 ms

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

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