Seattle, USA → New York, USA RTT
ICMP round-trip time measurements from Seattle, USA to New York, USA: average 59 ms, 0% loss, and stability details. Explore raw latency data.
🇺🇸 Seattle, USA (SEA) → 🇺🇸 New York, USA (NYC)
Measurement round: 2026-08-15T04:03:13Z.
The 2026-08-15T04:03:13Z ICMP echo RTT test from Seattle to New York averaged 59 ms over 50 samples, with a 57.69 ms minimum, 64.3 ms maximum, and zero packet loss.
The 1.27 ms standard deviation and 0.95 ms jitter signal a very stable transcontinental path. The measured average is 1.55 times the 37.95 ms fiber-floor estimate for the 3,875.5 km geodesic distance, putting fiber efficiency at about 64.3%.
This destination ranks 2nd out of 19 outbound routes from this source by typical latency, and its RTT spread is smaller relative to the average than the network-wide median variability of 3.08%. The close grouping of all 50 samples makes this a strong low-variance cross-country reference.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 59 ms |
| Jitter | 0.95 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 37.95 ms |
| Fiber Efficiency | 64.3% |
| Latency Tier | Excellent |
| 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 → NYC
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 59.0 ± 0.18 ms (SE)
Sample distribution: box = interquartile range (58.2–59.3 ms), median 58.6 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 (38.0 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 57.87 |
| 2 | 100 | 58.43 |
| 3 | 200 | 58.20 |
| 4 | 300 | 57.72 |
| 5 | 400 | 57.69 |
| 6 | 500 | 58.28 |
| 7 | 600 | 58.91 |
| 8 | 700 | 58.53 |
| 9 | 800 | 64.30 |
| 10 | 900 | 62.13 |
| 11 | 1000 | 59.37 |
| 12 | 1100 | 59.99 |
| 13 | 1200 | 59.00 |
| 14 | 1300 | 58.60 |
| 15 | 1400 | 58.31 |
| 16 | 1500 | 57.84 |
| 17 | 1600 | 57.78 |
| 18 | 1700 | 57.87 |
| 19 | 1800 | 58.49 |
| 20 | 1900 | 58.96 |
| 21 | 2000 | 58.18 |
| 22 | 2100 | 60.44 |
| 23 | 2200 | 59.80 |
| 24 | 2300 | 58.83 |
| 25 | 2400 | 57.95 |
| 26 | 2500 | 59.19 |
| 27 | 2600 | 60.49 |
| 28 | 2700 | 59.12 |
| 29 | 2800 | 59.16 |
| 30 | 2900 | 59.33 |
| 31 | 3000 | 58.65 |
| 32 | 3100 | 59.53 |
| 33 | 3200 | 59.23 |
| 34 | 3300 | 58.28 |
| 35 | 3400 | 57.77 |
| 36 | 3500 | 58.22 |
| 37 | 3600 | 57.96 |
| 38 | 3700 | 58.45 |
| 39 | 3800 | 61.99 |
| 40 | 3900 | 59.72 |
| 41 | 4000 | 58.27 |
| 42 | 4100 | 58.36 |
| 43 | 4200 | 58.59 |
| 44 | 4300 | 58.83 |
| 45 | 4400 | 59.41 |
| 46 | 4500 | 61.58 |
| 47 | 4600 | 59.21 |
| 48 | 4700 | 58.07 |
| 49 | 4800 | 58.70 |
| 50 | 4900 | 58.42 |
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 New York City (40.71427, -74.00597). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 3,875.5 km |
| Vacuum RTT floor | 25.85 ms |
| Standard fiber RTT floor () | 37.95 ms |
| Low-latency fiber material floor | 37.8 ms |
| Engineering floor (5% path allowance) | 39.85 ms |
| Research 1.33× mapped-fiber reference | 50.48 ms |
| Estimated unamplified path loss | 813.9 dB |
| Transparent optical spans / inline amplifiers | 51 / 50 |
| Published RTT inflation over fiber floor | 1.55× |
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 | 57.69 ms |
| Average RTT | 59 ms |
| Maximum RTT | 64.3 ms |
| Standard deviation | 1.27 ms |
| Stdev / average | 2.2% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 59.0 ms
- Minimum
- 58.4 ms
- Maximum
- 59.5 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: New York (NYC)
- Region overview: North America → North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
Fastest routes departing Seattle (SEA)
- Seattle to Los Angeles latency and RTT — 26.6 ms
- Seattle to Ashburn latency and RTT — 62 ms
- Seattle to Miami latency and RTT — 81.1 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
- Seattle to Taipei latency and RTT — 115.1 ms
Fastest routes arriving at New York (NYC)
- Ashburn to New York latency and RTT — 6 ms
- Miami to New York latency and RTT — 34 ms
- Los Angeles to New York latency and RTT — 59 ms
- London to New York latency and RTT — 63.5 ms
- Amsterdam to New York latency and RTT — 68.2 ms
Same corridor (North America → North America)
- New York to Ashburn latency and RTT — 6 ms
- Miami to Ashburn latency and RTT — 27.3 ms
- Los Angeles to Seattle latency and RTT — 27.5 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-nyc.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → New York 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.