# Amsterdam, Netherlands → Taipei, Taiwan RTT

🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇹🇼 **Taipei, Taiwan (TPE)**

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

For round 2026-08-16T04:07:28Z, ICMP echo probes from Amsterdam to Taipei averaged 168.7 ms, with a minimum of 163.09 ms and a maximum of 184.23 ms over 50 samples and zero packet loss.

The 9,467.8 km geodesic distance sets a vacuum floor of 63.16 ms and a fiber floor of 92.72 ms. At 168.7 ms, the average is 1.82 times the fiber floor, which puts the route at 55% fiber efficiency and indicates more overhead than a direct straight-line fiber path would allow.

Within the round's 19 outbound routes from Amsterdam, this path ranked 14th. Its standard deviation of 4.36 ms is about 2.6% of the average—lower than the 3.28% median variation across the network's outbound route set—so the latency profile is more consistent than typical for this peer group.

The useful takeaway is that Amsterdam-Taipei RTTs are moderate and stable rather than extreme: the 168.7 ms baseline is driven mainly by distance and route overhead, while jitter of 3.84 ms and the zero-loss result reinforce that the path is steady in this round.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **168.7 ms**                                               |
| Jitter               | **3.84 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **92.72 ms**                                               |
| Fiber Efficiency     | **55%**                                                    |
| 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 [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) 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                      | **9,467.8 km** |
| Vacuum RTT floor                              | **63.16 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **92.72 ms**   |
| Low-latency fiber material floor              | **92.34 ms**   |
| Engineering floor (5% path allowance)         | **97.36 ms**   |
| Research 1.33× mapped-fiber reference         | **123.31 ms**  |
| Estimated unamplified path loss               | **1988.2 dB**  |
| Transparent optical spans / inline amplifiers | **125 / 124**  |
| Published RTT inflation over fiber floor      | **1.82×**      |

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        | **163.09 ms** |
| Average RTT        | **168.7 ms**  |
| Maximum RTT        | **184.23 ms** |
| Standard deviation | **4.36 ms**   |
| Stdev / average    | **2.6%**      |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* 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 Amsterdam latency and RTT](/docs/network/latency/pairs/tpe-ams-rtt) — 166.5 ms

**Fastest routes departing Amsterdam (AMS)**

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