# Berlin, Germany → Taipei, Taiwan RTT

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

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

ICMP echo round-trip time from Berlin, Germany to Taipei, Taiwan in the 2026-08-16T04:07:28Z round averaged 156.8ms, with a minimum of 150.23ms and a maximum of 174.22ms from 50 samples. Jitter was 4.24ms and packet loss was 0%, so the path was both moderate in latency and clean during the window.

The measured average is 1.78 times the 87.84ms fiber-floor estimate for the 8,970.4km geodesic, adding about 68.9ms of overhead above the theoretical minimum. With fiber efficiency at 56%, the route sits in the Fair latency tier while carrying a noticeable gap from the theoretical floor.

This route is 13th among the 19 outbound routes in the round, while the network-wide median variability relative to the average is 3.28%. The route's own standard deviation of 5.07ms is about 3.23% of the average, placing its variability almost exactly in line with the network median.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **156.8 ms**                                               |
| Jitter               | **4.24 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **87.84 ms**                                               |
| Fiber Efficiency     | **56%**                                                    |
| Latency Tier         | Fair                                                       |
| Source Region        | [Europe](/docs/network/latency/regions/europe)             |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |

## 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). 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.78×**      |

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        | **150.23 ms** |
| Average RTT        | **156.8 ms**  |
| Maximum RTT        | **174.22 ms** |
| Standard deviation | **5.07 ms**   |
| Stdev / average    | **3.2%**      |

## Route Context

* Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-to-asia-pacific)
* 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**

* [Taipei to Berlin latency and RTT](/docs/network/latency/pairs/tpe-ber-rtt) — 158.6 ms

**Fastest routes departing Berlin (BER)**

* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms
* [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms

**Fastest routes arriving at Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms

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

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.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/ber-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Taipei 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/ber-tpe-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.