Frankfurt, Germany → Seattle, USA RTT
Frankfurt, Germany to Seattle, USA ICMP RTT: 134 ms average, 128.47–150.15 ms range, zero packet loss across 50 samples.
🇩🇪 Frankfurt, Germany (FRA) → 🇺🇸 Seattle, USA (SEA)
Measurement round: 2026-08-15T04:03:13Z.
Round 2026-08-15T04:03:13Z measured Frankfurt, Germany to Seattle, USA at 134 ms average ICMP RTT, with a 128.47 ms minimum and 150.15 ms maximum across 50 samples and zero packet loss.
Spanning an 8,204 km great-circle distance, the theoretical vacuum round trip is 54.73 ms and the fiber-limited floor is 80.34 ms; the observed 134 ms is 1.67 times that floor, placing fiber efficiency near 60%, a solid result for a long intercontinental path.
This route ranked 10th among the 19 outbound routes in the same round. Its 5 ms standard deviation and 3.99 ms jitter are consistent with the round's median spread of 3.08% of average latency, giving the Good tier a stable, predictable character.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 134 ms |
| Jitter | 3.99 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 80.34 ms |
| Fiber Efficiency | 60% |
| Latency Tier | Good |
| Source Region | Europe |
| 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: FRA → SEA
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 134.0 ± 0.71 ms (SE)
Sample distribution: box = interquartile range (130.0–136.7 ms), median 132.5 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 (80.3 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 138.90 |
| 2 | 100 | 135.25 |
| 3 | 200 | 130.27 |
| 4 | 300 | 135.42 |
| 5 | 400 | 135.62 |
| 6 | 500 | 131.26 |
| 7 | 600 | 136.37 |
| 8 | 700 | 130.71 |
| 9 | 800 | 139.13 |
| 10 | 900 | 150.15 |
| 11 | 1000 | 139.36 |
| 12 | 1100 | 133.18 |
| 13 | 1200 | 130.18 |
| 14 | 1300 | 128.47 |
| 15 | 1400 | 128.96 |
| 16 | 1500 | 129.34 |
| 17 | 1600 | 129.96 |
| 18 | 1700 | 132.03 |
| 19 | 1800 | 140.66 |
| 20 | 1900 | 137.89 |
| 21 | 2000 | 131.30 |
| 22 | 2100 | 130.22 |
| 23 | 2200 | 130.00 |
| 24 | 2300 | 129.02 |
| 25 | 2400 | 139.23 |
| 26 | 2500 | 149.05 |
| 27 | 2600 | 139.79 |
| 28 | 2700 | 132.33 |
| 29 | 2800 | 129.28 |
| 30 | 2900 | 129.62 |
| 31 | 3000 | 129.98 |
| 32 | 3100 | 130.51 |
| 33 | 3200 | 128.74 |
| 34 | 3300 | 132.87 |
| 35 | 3400 | 135.51 |
| 36 | 3500 | 130.43 |
| 37 | 3600 | 136.87 |
| 38 | 3700 | 133.40 |
| 39 | 3800 | 134.73 |
| 40 | 3900 | 137.66 |
| 41 | 4000 | 144.18 |
| 42 | 4100 | 134.97 |
| 43 | 4200 | 133.64 |
| 44 | 4300 | 132.64 |
| 45 | 4400 | 131.95 |
| 46 | 4500 | 129.91 |
| 47 | 4600 | 129.20 |
| 48 | 4700 | 128.60 |
| 49 | 4800 | 132.36 |
| 50 | 4900 | 138.90 |
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 Frankfurt am Main (50.11552, 8.68417) and Seattle (47.60621, -122.33207). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 8,204 km |
| Vacuum RTT floor | 54.73 ms |
| Standard fiber RTT floor () | 80.34 ms |
| Low-latency fiber material floor | 80.02 ms |
| Engineering floor (5% path allowance) | 84.37 ms |
| Research 1.33× mapped-fiber reference | 106.85 ms |
| Estimated unamplified path loss | 1722.8 dB |
| Transparent optical spans / inline amplifiers | 108 / 107 |
| Published RTT inflation over fiber floor | 1.67× |
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 | 128.47 ms |
| Average RTT | 134 ms |
| Maximum RTT | 150.15 ms |
| Standard deviation | 5 ms |
| Stdev / average | 3.7% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 134.1 ms
- Minimum
- 132.8 ms
- Maximum
- 135.2 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Frankfurt (FRA)
- Destination PoP: Seattle (SEA)
- Region overview: Europe → North America
- Corridor overview: Europe to North America
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Seattle to Frankfurt latency and RTT — 133 ms
Fastest routes departing Frankfurt (FRA)
- Frankfurt to Amsterdam latency and RTT — 5.9 ms
- Frankfurt to Berlin latency and RTT — 6.1 ms
- Frankfurt to Paris latency and RTT — 7.6 ms
- Frankfurt to London latency and RTT — 12.6 ms
- Frankfurt to Marseille latency and RTT — 17.2 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
- Miami to Seattle latency and RTT — 82 ms
- Tokyo to Seattle latency and RTT — 84.6 ms
Same corridor (Europe → North America)
- London to New York latency and RTT — 63.5 ms
- Amsterdam to New York latency and RTT — 68.2 ms
- Paris to New York latency and RTT — 68.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/fra-sea.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → 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.