# London, UK → Seattle, USA RTT

🇬🇧 &#x2A;*London, UK (LON)** → 🇺🇸 &#x2A;*Seattle, USA (SEA)**

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

In the 2026-08-16T04:07:28Z round, London-to-Seattle produced an average ICMP echo RTT of 123.2 ms from 50 samples, with a minimum of 121.09 ms and a maximum of 129.68 ms.

The 1.95 ms standard deviation and 1.63 ms jitter point to a stable route, and zero packet loss accompanies the good latency tier. Over the 7,722.7 km great-circle distance, the fiber floor is 75.63 ms, so the measured average is 1.63 times that floor and fiber efficiency is 61.4%.

This route ranks 10th among the 19 routes measured in this round. Its standard deviation is only 1.58% of the average, well below the median of 3.28% across the measured route set, making it one of the more consistent routes in the set despite the longer geographic span.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **123.2 ms**                                                 |
| Jitter               | **1.63 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **75.63 ms**                                                 |
| Fiber Efficiency     | **61.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 [London](https://www.geonames.org/2643743) (51.50853, -0.12574) 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                      | **7,722.7 km** |
| Vacuum RTT floor                              | **51.52 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **75.63 ms**   |
| Low-latency fiber material floor              | **75.32 ms**   |
| Engineering floor (5% path allowance)         | **79.42 ms**   |
| Research 1.33× mapped-fiber reference         | **100.58 ms**  |
| Estimated unamplified path loss               | **1621.8 dB**  |
| Transparent optical spans / inline amplifiers | **102 / 101**  |
| Published RTT inflation over fiber floor      | **1.63×**      |

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        | **121.09 ms** |
| Average RTT        | **123.2 ms**  |
| Maximum RTT        | **129.68 ms** |
| Standard deviation | **1.95 ms**   |
| Stdev / average    | **1.6%**      |

## Route Context

* Departure PoP: [London (LON)](/docs/network/latency/lon-london)
* 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 London latency and RTT](/docs/network/latency/pairs/sea-lon-rtt) — 124.1 ms

**Fastest routes departing London (LON)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [London to Paris latency and RTT](/docs/network/latency/pairs/lon-par-rtt) — 6.4 ms
* [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms
* [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms
* [London to Marseille latency and RTT](/docs/network/latency/pairs/lon-mrs-rtt) — 17.9 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/lon-sea.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, London → 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/lon-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.
