# Taipei, Taiwan → London, UK RTT

🇹🇼 &#x2A;*Taipei, Taiwan (TPE)** → 🇬🇧 &#x2A;*London, UK (LON)**

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

For the 2026-08-16T04:07:28Z round, 50 ICMP echo probes from Taipei to London completed with an average RTT of 173 ms, a minimum of 165.18 ms, and a maximum of 197.84 ms. The path carried no packet loss, while its 6.02 ms standard deviation and 4.56 ms jitter suggest the latency remained fairly consistent throughout the sample.

At 173 ms, the measured RTT is about 1.8 times the 95.97 ms fiber floor calculated from the 9,799.7 km great-circle distance, placing the route's fiber efficiency at roughly 55.5%. That gap is expected for an intercontinental journey, and the instability is modest rather than dramatic.

Within the network's broader route set, this Taipei-to-London path ranks 13th among the 19 routes compared by typical latency. Its variability as a share of average latency is close to the network's 3.28% median coefficient of variation for such measurements, so operators can read this as a mid-ranking but steady connection for the measured ICMP traffic.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **173 ms**                                                 |
| Jitter               | **4.56 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **95.97 ms**                                               |
| Fiber Efficiency     | **55.5%**                                                  |
| Latency Tier         | Fair                                                       |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Europe](/docs/network/latency/regions/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.

## 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 [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,799.7 km** |
| Vacuum RTT floor                              | **65.38 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **95.97 ms**   |
| Low-latency fiber material floor              | **95.58 ms**   |
| Engineering floor (5% path allowance)         | **100.78 ms**  |
| Research 1.33× mapped-fiber reference         | **127.63 ms**  |
| Estimated unamplified path loss               | **2057.9 dB**  |
| Transparent optical spans / inline amplifiers | **129 / 128**  |
| Published RTT inflation over fiber floor      | **1.8×**       |

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        | **165.18 ms** |
| Average RTT        | **173 ms**    |
| Maximum RTT        | **197.84 ms** |
| Standard deviation | **6.02 ms**   |
| Stdev / average    | **3.5%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Destination PoP: [London (LON)](/docs/network/latency/lon-london)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe)
* 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**

* [London to Taipei latency and RTT](/docs/network/latency/pairs/lon-tpe-rtt) — 173.8 ms

**Fastest routes departing Taipei (TPE)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms
* [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms
* [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms

**Fastest routes arriving at London (LON)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 ms

**Same corridor (Asia Pacific → Europe)**

* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms
* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms
* [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → London 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/tpe-lon-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.
