# Frankfurt, Germany → Seattle, USA RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Seattle, USA (SEA)**

Measurement round: `2026-08-16T04:07:28Z`.

In the 2026-08-16T04:07:28Z round, ICMP echo probes from Frankfurt to Seattle averaged 135.2 ms across 50 samples, with a minimum of 129.14 ms, a maximum of 151.39 ms and no packet loss. A standard deviation of 5.97 ms and jitter of 4.05 ms put this route's variability above the 3.28% median variability for the 19-route set.

Ranked 10th of 19 outbound routes by average RTT, this route sits near the middle of the set. The 135.2 ms average is 1.68 times the theoretical fiber floor of 80.34 ms for the 8,204 km great-circle distance, which corresponds to a fiber efficiency of 59.4%; the numbers show meaningful headroom relative to the idealized path.

With zero loss and moderate jitter, the 135.2 ms average is a stable baseline for this intercontinental route, even though its variability is somewhat higher than the set's median.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **135.2 ms**                                                 |
| Jitter               | **4.05 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **80.34 ms**                                                 |
| Fiber Efficiency     | **59.4%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [Europe](/docs/network/latency/regions/europe)               |
| Destination Region   | [North America](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) and [Seattle](https://www.geonames.org/5809844) (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 ($n_g=1.4679$)       | **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.68×**     |

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](/docs/network/latency/theoretical-fiber-latency).

## Stability & Trend

The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

| Round Statistic    | Value         |
| ------------------ | ------------- |
| Minimum RTT        | **129.14 ms** |
| Average RTT        | **135.2 ms**  |
| Maximum RTT        | **151.39 ms** |
| Standard deviation | **5.97 ms**   |
| Stdev / average    | **4.4%**      |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america)
* Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Seattle to Frankfurt latency and RTT](/docs/network/latency/pairs/sea-fra-rtt) — 133.2 ms

**Fastest routes departing Frankfurt (FRA)**

* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms
* [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms
* [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms

**Fastest routes arriving at Seattle (SEA)**

* [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms
* [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms
* [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms

**Same corridor (Europe → North America)**

* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms
* [Amsterdam to New York latency and RTT](/docs/network/latency/pairs/ams-nyc-rtt) — 68.6 ms
* [Paris to New York latency and RTT](/docs/network/latency/pairs/par-nyc-rtt) — 68.9 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](/opendata/latency/). 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-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/fra-sea-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.