Taipei, Taiwan → Amsterdam, Netherlands RTT
ICMP round-trip time page for Taipei, Taiwan to Amsterdam, Netherlands: average 167.4 ms, jitter 7.06 ms, no packet loss, 2026-08-15T04:03:13Z.
🇹🇼 Taipei, Taiwan (TPE) → 🇳🇱 Amsterdam, Netherlands (AMS)
Measurement round: 2026-08-15T04:03:13Z.
In the 2026-08-15T04:03:13Z round, 50 ICMP probes from Taipei, Taiwan to Amsterdam, Netherlands returned an average of 167.4 ms, with all samples completed and zero packet loss.
This route is ranked 11th among the 19 routes measured in the same round. Its standard deviation of 7.79 ms gives relative variability of 4.7%, above the 3.08% median for the set.
The average is 1.81 times the straight-line fiber floor of 92.72 ms over a geodesic distance of 9,467.8 km, yielding 55.4% fiber efficiency. The zero loss count and fair latency classification make it a stable intercontinental path, though its sample-to-sample spread is above the route set's typical level.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 167.4 ms |
| Jitter | 7.06 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 92.72 ms |
| Fiber Efficiency | 55.4% |
| Latency Tier | Fair |
| Source Region | Asia Pacific |
| Destination Region | 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.
Ping series: TPE → AMS
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 167.4 ± 1.10 ms (SE)
Sample distribution: box = interquartile range (161.8–169.7 ms), median 165.8 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (92.7 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 161.49 |
| 2 | 100 | 159.77 |
| 3 | 200 | 165.60 |
| 4 | 300 | 165.74 |
| 5 | 400 | 186.06 |
| 6 | 500 | 168.80 |
| 7 | 600 | 162.03 |
| 8 | 700 | 184.22 |
| 9 | 800 | 171.37 |
| 10 | 900 | 162.08 |
| 11 | 1000 | 163.59 |
| 12 | 1100 | 184.94 |
| 13 | 1200 | 167.75 |
| 14 | 1300 | 177.18 |
| 15 | 1400 | 172.24 |
| 16 | 1500 | 168.23 |
| 17 | 1600 | 161.71 |
| 18 | 1700 | 161.25 |
| 19 | 1800 | 161.11 |
| 20 | 1900 | 163.09 |
| 21 | 2000 | 159.36 |
| 22 | 2100 | 162.11 |
| 23 | 2200 | 166.13 |
| 24 | 2300 | 164.77 |
| 25 | 2400 | 168.47 |
| 26 | 2500 | 166.88 |
| 27 | 2600 | 162.11 |
| 28 | 2700 | 159.04 |
| 29 | 2800 | 157.78 |
| 30 | 2900 | 167.79 |
| 31 | 3000 | 161.38 |
| 32 | 3100 | 159.17 |
| 33 | 3200 | 163.29 |
| 34 | 3300 | 180.13 |
| 35 | 3400 | 167.18 |
| 36 | 3500 | 165.83 |
| 37 | 3600 | 160.56 |
| 38 | 3700 | 160.04 |
| 39 | 3800 | 161.76 |
| 40 | 3900 | 162.57 |
| 41 | 4000 | 167.20 |
| 42 | 4100 | 162.40 |
| 43 | 4200 | 189.63 |
| 44 | 4300 | 174.72 |
| 45 | 4400 | 167.11 |
| 46 | 4500 | 165.83 |
| 47 | 4600 | 184.53 |
| 48 | 4700 | 173.92 |
| 49 | 4800 | 170.02 |
| 50 | 4900 | 170.04 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Taipei (25.05306, 121.52639) and Amsterdam (52.37403, 4.88969). 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 () | 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.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.
Stability & Trend
The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 157.78 ms |
| Average RTT | 167.4 ms |
| Maximum RTT | 189.63 ms |
| Standard deviation | 7.79 ms |
| Stdev / average | 4.7% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 167.5 ms
- Minimum
- 165.6 ms
- Maximum
- 169.2 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Taipei (TPE)
- Destination PoP: Amsterdam (AMS)
- Region overview: Asia Pacific → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Amsterdam to Taipei latency and RTT — 167.2 ms
Fastest routes departing Taipei (TPE)
- Taipei to Hong Kong latency and RTT — 15.4 ms
- Taipei to Tokyo latency and RTT — 31.6 ms
- Taipei to Singapore latency and RTT — 44.2 ms
- Taipei to Seattle latency and RTT — 115.7 ms
- Taipei to Moscow latency and RTT — 131.7 ms
Fastest routes arriving at Amsterdam (AMS)
- London to Amsterdam latency and RTT — 5.1 ms
- Frankfurt to Amsterdam latency and RTT — 5.9 ms
- Paris to Amsterdam latency and RTT — 7 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Marseille to Amsterdam latency and RTT — 19.6 ms
Same corridor (Asia Pacific → Europe)
- Hong Kong to Moscow latency and RTT — 116.6 ms
- Singapore to Marseille latency and RTT — 138.8 ms
- Hong Kong to Berlin latency and RTT — 143.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. Per-pair files are available at /opendata/latency/latest/pairs/tpe-ams.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Amsterdam round 2026-08-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.