# Taipei, Taiwan → Frankfurt, Germany RTT

🇹🇼 **Taipei, Taiwan (TPE)** → 🇩🇪 **Frankfurt, Germany (FRA)**

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

In the 2026-08-16T04:07:28Z sample, ICMP echo requests between Taipei, Taiwan and Frankfurt, Germany returned an average round-trip time of 166 ms. The minimum was 162.67 ms, the maximum was 174.81 ms, and none of the 50 packets were lost; with a standard deviation of 2.89 ms and jitter of 2.22 ms, the route was consistent over the measurement window.

The geodesic distance for this city pair is 9,390.8 km, which puts the theoretical vacuum round-trip floor at 62.65 ms and the optical-fiber floor at 91.96 ms. The measured 166 ms average is 1.81 times that fiber floor; equivalently, the fiber floor accounts for 55.4% of the observed RTT. The delay is therefore well above the floor while remaining stable and loss-free.

This route was 10th of the 19 outbound paths in its measured set, placing it around the median position rather than at either extreme. Its own variability, a 2.89 ms standard deviation against a 166 ms average, is about 1.7%, lower than the 3.28% median variability ratio for the same outbound set. The useful takeaway is that, in this sample, Frankfurt-bound latency from Taipei is moderate in absolute terms but notably stable.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **166 ms**                                                 |
| Jitter               | **2.22 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **91.96 ms**                                               |
| Fiber Efficiency     | **55.4%**                                                  |
| 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 [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,390.8 km** |
| Vacuum RTT floor                              | **62.65 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **91.96 ms**   |
| Low-latency fiber material floor              | **91.59 ms**   |
| Engineering floor (5% path allowance)         | **96.57 ms**   |
| Research 1.33× mapped-fiber reference         | **122.31 ms**  |
| Estimated unamplified path loss               | **1972.1 dB**  |
| Transparent optical spans / inline amplifiers | **124 / 123**  |
| Published RTT inflation over fiber floor      | **1.81×**      |

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        | **162.67 ms** |
| Average RTT        | **166 ms**    |
| Maximum RTT        | **174.81 ms** |
| Standard deviation | **2.89 ms**   |
| Stdev / average    | **1.7%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* 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**

* [Frankfurt to Taipei latency and RTT](/docs/network/latency/pairs/fra-tpe-rtt) — 163.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 Frankfurt (FRA)**

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