Seattle, USA → Frankfurt, Germany RTT
Seattle (USA) to Frankfurt (Germany) ICMP RTT measurement: average 133 ms, jitter 4.44 ms, standard deviation 5.03 ms, 0% loss, round 2026-08-15.
🇺🇸 Seattle, USA (SEA) → 🇩🇪 Frankfurt, Germany (FRA)
Measurement round: 2026-08-15T04:03:13Z.
ICMP echo RTT from Seattle to Frankfurt in the 2026-08-15T04:03:13Z round averaged 133 ms, with samples ranging from 126.42 ms to 148.49 ms. There was no packet loss; jitter was 4.44 ms.
For the 8,204 km great-circle distance, the fiber-floor estimate is 80.34 ms, and the measured average is 1.66 times that floor, or 60.4% fiber efficiency. Frankfurt's role as a central switching point means the route ends in one of Europe's major interconnection environments, where the extra delay over the floor reflects the long-haul crossing needed to reach that hub.
This route ranked 11th fastest among the 19 routes leaving Seattle in the same round. Its standard deviation of 5.03 ms is about 3.8% of the average RTT, above the 3.08% median variation for the route set, so short-term changes in delay matter more than the route's middle-of-pack ranking suggests.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 133 ms |
| Jitter | 4.44 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 80.34 ms |
| Fiber Efficiency | 60.4% |
| Latency Tier | Good |
| Source Region | North America |
| Destination Region | Europe |
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 → FRA
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 133.0 ± 0.71 ms (SE)
Sample distribution: box = interquartile range (129.1–135.5 ms), median 131.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 | 126.42 |
| 2 | 100 | 129.84 |
| 3 | 200 | 127.77 |
| 4 | 300 | 131.49 |
| 5 | 400 | 129.00 |
| 6 | 500 | 135.54 |
| 7 | 600 | 133.56 |
| 8 | 700 | 133.11 |
| 9 | 800 | 131.13 |
| 10 | 900 | 128.94 |
| 11 | 1000 | 132.29 |
| 12 | 1100 | 127.96 |
| 13 | 1200 | 126.96 |
| 14 | 1300 | 134.89 |
| 15 | 1400 | 138.38 |
| 16 | 1500 | 130.12 |
| 17 | 1600 | 130.00 |
| 18 | 1700 | 136.74 |
| 19 | 1800 | 130.97 |
| 20 | 1900 | 128.42 |
| 21 | 2000 | 144.76 |
| 22 | 2100 | 135.68 |
| 23 | 2200 | 134.25 |
| 24 | 2300 | 146.34 |
| 25 | 2400 | 138.76 |
| 26 | 2500 | 139.81 |
| 27 | 2600 | 135.36 |
| 28 | 2700 | 130.51 |
| 29 | 2800 | 127.86 |
| 30 | 2900 | 136.71 |
| 31 | 3000 | 132.03 |
| 32 | 3100 | 128.82 |
| 33 | 3200 | 135.30 |
| 34 | 3300 | 136.97 |
| 35 | 3400 | 137.10 |
| 36 | 3500 | 130.80 |
| 37 | 3600 | 131.66 |
| 38 | 3700 | 130.44 |
| 39 | 3800 | 134.87 |
| 40 | 3900 | 131.44 |
| 41 | 4000 | 127.72 |
| 42 | 4100 | 134.65 |
| 43 | 4200 | 131.33 |
| 44 | 4300 | 129.37 |
| 45 | 4400 | 130.00 |
| 46 | 4500 | 128.50 |
| 47 | 4600 | 126.68 |
| 48 | 4700 | 128.32 |
| 49 | 4800 | 148.49 |
| 50 | 4900 | 141.94 |
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 Frankfurt am Main (50.11552, 8.68417). 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.66× |
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 | 126.42 ms |
| Average RTT | 133 ms |
| Maximum RTT | 148.49 ms |
| Standard deviation | 5.03 ms |
| Stdev / average | 3.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 132.8 ms
- Minimum
- 131.5 ms
- Maximum
- 133.9 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: Frankfurt (FRA)
- Region overview: North America → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Frankfurt to Seattle latency and RTT — 134 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 Miami latency and RTT — 81.1 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
Fastest routes arriving at Frankfurt (FRA)
- Amsterdam to Frankfurt latency and RTT — 5.9 ms
- Berlin to Frankfurt latency and RTT — 6.1 ms
- Paris to Frankfurt latency and RTT — 7.6 ms
- London to Frankfurt latency and RTT — 12.3 ms
- Marseille to Frankfurt latency and RTT — 17.5 ms
Same corridor (North America → Europe)
- New York to London latency and RTT — 64.3 ms
- New York to Paris latency and RTT — 68.4 ms
- New York to Amsterdam latency and RTT — 68.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-fra.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Frankfurt 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.