Miami, USA → Seattle, USA RTT
Direct ICMP echo RTT measurement from Miami, USA to Seattle, USA: 82 ms average latency, 0% packet loss, 2.15 ms jitter over 50 samples.
🇺🇸 Miami, USA (MIA) → 🇺🇸 Seattle, USA (SEA)
Measurement round: 2026-08-15T04:03:13Z.
Measurement round 2026-08-15T04:03:13Z collected 50 ICMP echo round trips from Miami to Seattle every 100 ms, yielding an 82 ms average, a 79.01 ms minimum, and a 90.39 ms maximum. Zero packet loss and 2.15 ms jitter indicate a clean long-haul connection.
The route ranked fourth among the 19 outbound routes in this set. Its 2.43 ms standard deviation is about 2.96% of the average, slightly below the 3.08% median standard-deviation-to-average ratio for those routes, so the cross-country link stays within a tight envelope.
With a 4,399.4 km great-circle distance, the fiber-floor estimate is 43.08 ms. The 82 ms average is 1.90 times that floor, and the 52.5% fiber efficiency quantifies the overhead across the long coast-to-coast span.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 82 ms |
| Jitter | 2.15 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 43.08 ms |
| Fiber Efficiency | 52.5% |
| 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: MIA → SEA
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 82.0 ± 0.34 ms (SE)
Sample distribution: box = interquartile range (80.3–83.2 ms), median 81.3 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 | 79.03 |
| 2 | 100 | 83.89 |
| 3 | 200 | 83.13 |
| 4 | 300 | 84.13 |
| 5 | 400 | 80.58 |
| 6 | 500 | 79.79 |
| 7 | 600 | 81.64 |
| 8 | 700 | 80.79 |
| 9 | 800 | 85.02 |
| 10 | 900 | 81.50 |
| 11 | 1000 | 81.99 |
| 12 | 1100 | 84.16 |
| 13 | 1200 | 83.08 |
| 14 | 1300 | 80.11 |
| 15 | 1400 | 80.79 |
| 16 | 1500 | 80.96 |
| 17 | 1600 | 85.56 |
| 18 | 1700 | 82.69 |
| 19 | 1800 | 81.37 |
| 20 | 1900 | 88.76 |
| 21 | 2000 | 83.25 |
| 22 | 2100 | 81.59 |
| 23 | 2200 | 81.52 |
| 24 | 2300 | 84.23 |
| 25 | 2400 | 83.98 |
| 26 | 2500 | 83.87 |
| 27 | 2600 | 80.46 |
| 28 | 2700 | 81.37 |
| 29 | 2800 | 81.25 |
| 30 | 2900 | 90.39 |
| 31 | 3000 | 85.44 |
| 32 | 3100 | 81.05 |
| 33 | 3200 | 80.44 |
| 34 | 3300 | 80.22 |
| 35 | 3400 | 79.11 |
| 36 | 3500 | 79.03 |
| 37 | 3600 | 79.01 |
| 38 | 3700 | 81.04 |
| 39 | 3800 | 79.81 |
| 40 | 3900 | 86.75 |
| 41 | 4000 | 82.88 |
| 42 | 4100 | 80.19 |
| 43 | 4200 | 80.53 |
| 44 | 4300 | 79.63 |
| 45 | 4400 | 82.18 |
| 46 | 4500 | 80.25 |
| 47 | 4600 | 80.31 |
| 48 | 4700 | 81.31 |
| 49 | 4800 | 80.12 |
| 50 | 4900 | 79.82 |
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 Miami (25.77427, -80.19366) and Seattle (47.60621, -122.33207). 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.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.
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 | 79.01 ms |
| Average RTT | 82 ms |
| Maximum RTT | 90.39 ms |
| Standard deviation | 2.43 ms |
| Stdev / average | 3.0% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 82.0 ms
- Minimum
- 81.3 ms
- Maximum
- 82.8 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: Miami (MIA)
- Destination PoP: Seattle (SEA)
- Region overview: North America → North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Seattle to Miami latency and RTT — 81.1 ms
Fastest routes departing Miami (MIA)
- Miami to Ashburn latency and RTT — 27.3 ms
- Miami to New York latency and RTT — 34 ms
- Miami to Los Angeles latency and RTT — 56.8 ms
- Miami to London latency and RTT — 100.7 ms
- Miami to Paris latency and RTT — 105.4 ms
Fastest routes arriving at Seattle (SEA)
- Los Angeles to Seattle latency and RTT — 27.5 ms
- New York to Seattle latency and RTT — 59 ms
- Ashburn to Seattle latency and RTT — 61.3 ms
- Tokyo to Seattle latency and RTT — 84.6 ms
- Taipei to Seattle latency and RTT — 115.7 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
- Seattle to Los Angeles latency and RTT — 26.6 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/mia-sea.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Seattle 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.