# Taipei, Taiwan → Berlin, Germany RTT

🇹🇼 **Taipei, Taiwan (TPE)** → 🇩🇪 **Berlin, Germany (BER)**

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

During the 2026-08-16T04:07:28Z run, ICMP echo probes from Taipei, Taiwan to Berlin, Germany averaged 158.6 ms over 50 samples, with a minimum of 154.12 ms and a maximum of 170.16 ms. No packets were lost, and jitter of 3.48 ms kept the round-trip times tightly grouped.

That average sits at 1.81 times the theoretical fiber-floor value for the 8,970.4 km great-circle path, which corresponds to a fiber efficiency of 55.4%. Even the fastest sample was 154.12 ms, so the floor is high: the route's Fair latency tier is shaped by geography and the optical distance that must be covered, not by sample-to-sample instability.

The 3.77 ms standard deviation is only about 2.4% of the route average, calmer than the 3.28% median variability-to-average ratio seen across the 19 outbound routes in this measurement group. Ranked 9th in that group, the Taipei–Berlin path offers a consistent, loss-free ICMP RTT profile that can be treated as predictable over short observation windows.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **158.6 ms**                                               |
| Jitter               | **3.48 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **87.84 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **8,970.4 km** |
| Vacuum RTT floor                              | **59.84 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **87.84 ms**   |
| Low-latency fiber material floor              | **87.49 ms**   |
| Engineering floor (5% path allowance)         | **92.25 ms**   |
| Research 1.33× mapped-fiber reference         | **116.83 ms**  |
| Estimated unamplified path loss               | **1883.8 dB**  |
| Transparent optical spans / inline amplifiers | **118 / 117**  |
| 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        | **154.12 ms** |
| Average RTT        | **158.6 ms**  |
| Maximum RTT        | **170.16 ms** |
| Standard deviation | **3.77 ms**   |
| Stdev / average    | **2.4%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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**

* [Berlin to Taipei latency and RTT](/docs/network/latency/pairs/ber-tpe-rtt) — 156.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 Berlin (BER)**

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