Seattle, USA → Miami, USA RTT
Seattle, USA to Miami, USA ICMP round-trip time measurement: 81.1 ms average, 0% loss, 50 samples, round 2026-08-15T04:03:13Z.
🇺🇸 Seattle, USA (SEA) → 🇺🇸 Miami, USA (MIA)
Measurement round: 2026-08-15T04:03:13Z.
In round 2026-08-15T04:03:13Z, Seattle-to-Miami ICMP echo RTT averaged 81.1 ms across 50 samples, with a minimum of 76.51 ms and a maximum of 94.5 ms. Zero packets were lost, but the 3.95 ms standard deviation and 2.79 ms jitter show the path is not perfectly uniform.
The route ranked fourth among the 19 outbound paths measured in this round, and its 4.9 percent relative dispersion sits above the group's median 3.08 percent. At 1.88 times the direct fiber floor for the 4,399.4 km great-circle distance, the path carries notable overhead, with fiber efficiency of 53.1 percent.
Despite the Good latency tier, the near-18 ms gap between minimum and maximum is the most useful signal: the path is consistently loss-free but occasionally adds delay at the tail. For a transcontinental route terminating in Miami's Latin American gateway, this round provides a realistic network-level RTT benchmark rather than an end-user performance promise.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 81.1 ms |
| Jitter | 2.79 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 43.08 ms |
| Fiber Efficiency | 53.1% |
| Latency Tier | Good |
| Source Region | North America |
| Destination Region | 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.
Ping series: SEA → MIA
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 81.1 ± 0.56 ms (SE)
Sample distribution: box = interquartile range (78.4–81.7 ms), median 80.4 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 (43.1 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 86.84 |
| 2 | 100 | 80.11 |
| 3 | 200 | 81.21 |
| 4 | 300 | 77.85 |
| 5 | 400 | 80.87 |
| 6 | 500 | 80.28 |
| 7 | 600 | 80.72 |
| 8 | 700 | 85.02 |
| 9 | 800 | 80.41 |
| 10 | 900 | 79.42 |
| 11 | 1000 | 78.37 |
| 12 | 1100 | 78.04 |
| 13 | 1200 | 77.66 |
| 14 | 1300 | 80.43 |
| 15 | 1400 | 78.76 |
| 16 | 1500 | 77.08 |
| 17 | 1600 | 76.51 |
| 18 | 1700 | 77.74 |
| 19 | 1800 | 78.93 |
| 20 | 1900 | 81.44 |
| 21 | 2000 | 81.14 |
| 22 | 2100 | 81.23 |
| 23 | 2200 | 80.97 |
| 24 | 2300 | 78.44 |
| 25 | 2400 | 79.09 |
| 26 | 2500 | 77.57 |
| 27 | 2600 | 76.65 |
| 28 | 2700 | 76.54 |
| 29 | 2800 | 79.84 |
| 30 | 2900 | 78.06 |
| 31 | 3000 | 77.18 |
| 32 | 3100 | 86.97 |
| 33 | 3200 | 85.60 |
| 34 | 3300 | 94.50 |
| 35 | 3400 | 83.67 |
| 36 | 3500 | 94.21 |
| 37 | 3600 | 87.83 |
| 38 | 3700 | 81.23 |
| 39 | 3800 | 88.53 |
| 40 | 3900 | 81.84 |
| 41 | 4000 | 81.10 |
| 42 | 4100 | 79.74 |
| 43 | 4200 | 81.99 |
| 44 | 4300 | 82.25 |
| 45 | 4400 | 80.55 |
| 46 | 4500 | 82.76 |
| 47 | 4600 | 79.36 |
| 48 | 4700 | 79.91 |
| 49 | 4800 | 77.79 |
| 50 | 4900 | 80.77 |
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 Seattle (47.60621, -122.33207) and Miami (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 () | 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.88× |
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-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 76.51 ms |
| Average RTT | 81.1 ms |
| Maximum RTT | 94.5 ms |
| Standard deviation | 3.95 ms |
| Stdev / average | 4.9% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 81.1 ms
- Minimum
- 80.2 ms
- Maximum
- 81.9 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: Miami (MIA)
- Region overview: North America → North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Miami to Seattle latency and RTT — 82 ms
Fastest routes departing Seattle (SEA)
- Seattle to Los Angeles latency and RTT — 26.6 ms
- Seattle to New York latency and RTT — 59 ms
- Seattle to Ashburn latency and RTT — 62 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
- Seattle to Taipei latency and RTT — 115.1 ms
Fastest routes arriving at Miami (MIA)
- Ashburn to Miami latency and RTT — 28.6 ms
- New York to Miami latency and RTT — 34.3 ms
- Los Angeles to Miami latency and RTT — 57.1 ms
- São Paulo to Miami latency and RTT — 74 ms
- London to Miami latency and RTT — 100.9 ms
Same corridor (North America → North America)
- Ashburn to New York latency and RTT — 6 ms
- New York to Ashburn latency and RTT — 6 ms
- Miami to Ashburn latency and RTT — 27.3 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/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-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.