Amsterdam (Netherlands) to Taipei (Taiwan) ICMP RTT summary: 168.7 ms average, 0% packet loss, 55% fiber efficiency for round 2026-08-16T04:07:28Z.

🇳🇱 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
Destination Region	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.

Ping series: AMS → TPE

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 168.7 ± 0.62 ms (SE)

Sample distribution: box = interquartile range (166.1–170.3 ms), median 167.3 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	164.05
2	100	163.09
3	200	164.28
4	300	165.80
5	400	166.71
6	500	166.00
7	600	168.17
8	700	174.51
9	800	170.35
10	900	167.82
11	1000	167.20
12	1100	167.42
13	1200	168.56
14	1300	168.76
15	1400	173.83
16	1500	166.49
17	1600	165.23
18	1700	174.03
19	1800	167.02
20	1900	164.77
21	2000	168.10
22	2100	169.12
23	2200	165.33
24	2300	171.33
25	2400	170.28
26	2500	177.65
27	2600	170.48
28	2700	170.04
29	2800	167.27
30	2900	165.29
31	3000	184.23
32	3100	170.25
33	3200	167.08
34	3300	166.57
35	3400	165.16
36	3500	163.61
37	3600	164.25
38	3700	165.36
39	3800	167.55
40	3900	171.80
41	4000	166.26
42	4100	167.28
43	4200	170.61
44	4300	182.96
45	4400	169.71
46	4500	166.60
47	4600	166.70
48	4700	168.17
49	4800	166.31
50	4900	175.56

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.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Amsterdam (52.37403, 4.88969) and Taipei (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.

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%

RTT trend

Estimated route stability across the selected time window.

Average: 168.8 ms
Minimum: 167.0 ms
Maximum: 170.2 ms
Average loss: 0.01%

Route Context

Departure PoP: Amsterdam (AMS)
Destination PoP: Taipei (TPE)
Region overview: Europe → Asia Pacific
Corridor overview: Europe to Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Taipei to Amsterdam latency and RTT — 166.5 ms

Fastest routes departing Amsterdam (AMS)

Amsterdam to London latency and RTT — 5.2 ms
Amsterdam to Frankfurt latency and RTT — 5.9 ms
Amsterdam to Paris latency and RTT — 7 ms
Amsterdam to Berlin latency and RTT — 7.2 ms
Amsterdam to Marseille latency and RTT — 19.6 ms

Fastest routes arriving at Taipei (TPE)

Hong Kong to Taipei latency and RTT — 14.7 ms
Tokyo to Taipei latency and RTT — 32.3 ms
Singapore to Taipei latency and RTT — 45.8 ms
Seattle to Taipei latency and RTT — 114.7 ms
Sydney to Taipei latency and RTT — 131.7 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 118.6 ms
Moscow to Taipei latency and RTT — 132.1 ms
Marseille to Singapore latency and 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. 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 or browse more city-pair routes.

Amsterdam, Netherlands → Taipei, Taiwan RTT