ICMP round-trip time from Taipei, Taiwan to Amsterdam, Netherlands: average 166.5 ms, 0% packet loss, jitter, and efficiency metrics.

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

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

For the 2026-08-16T04:07:28Z round, the Taipei, Taiwan to Amsterdam, Netherlands path averaged 166.5 ms over 50 ICMP echo samples, with a minimum of 161.36 ms, a maximum of 179.84 ms, and 0% packet loss. The standard deviation of 3.92 ms and jitter of 3.56 ms indicate a fairly stable connection during the test.

At a geodesic distance of roughly 9,467.8 km, the recorded average is 1.8 times the optical fiber floor of 92.72 ms, putting fiber efficiency at 55.7%. The extra delay over the floor is moderate for a route spanning this much geography, and the measured latency falls into the Fair tier.

This route ranked 11th among the 19 routes in the same round, and its 3.92 ms standard deviation equals about 2.4% of the average, below the 3.28% median variability across the monitored set. With zero packets lost and jitter under 4 ms, the Taipei–Amsterdam path is more consistent than its middle-of-the-pack absolute latency might suggest.

Latency Summary

Metric	Value
RTT	166.5 ms
Jitter	3.56 ms
Packet Loss	0%
Standard Fiber Floor	92.72 ms
Fiber Efficiency	55.7%
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-16T04:07:28Z · avg 166.5 ± 0.55 ms (SE)

Sample distribution: box = interquartile range (163.9–167.8 ms), median 166.1 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	175.50
2	100	166.33
3	200	163.41
4	300	166.03
5	400	164.73
6	500	167.26
7	600	167.67
8	700	164.29
9	800	161.36
10	900	163.26
11	1000	164.92
12	1100	163.76
13	1200	167.87
14	1300	166.02
15	1400	166.12
16	1500	162.50
17	1600	161.45
18	1700	176.28
19	1800	166.95
20	1900	163.57
21	2000	167.07
22	2100	175.28
23	2200	169.90
24	2300	169.48
25	2400	163.86
26	2500	162.02
27	2600	162.47
28	2700	167.80
29	2800	166.49
30	2900	166.30
31	3000	171.03
32	3100	167.79
33	3200	164.28
34	3300	162.70
35	3400	165.57
36	3500	179.84
37	3600	167.73
38	3700	167.92
39	3800	164.35
40	3900	166.43
41	4000	170.66
42	4100	171.25
43	4200	167.60
44	4300	164.46
45	4400	163.88
46	4500	163.96
47	4600	161.54
48	4700	165.34
49	4800	162.32
50	4900	166.40

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 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 ( $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.8×

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	161.36 ms
Average RTT	166.5 ms
Maximum RTT	179.84 ms
Standard deviation	3.92 ms
Stdev / average	2.4%

RTT trend

Estimated route stability across the selected time window.

Average: 166.5 ms
Minimum: 164.6 ms
Maximum: 168.3 ms
Average loss: 0.03%

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

Reverse direction

Amsterdam to Taipei latency and RTT — 168.7 ms

Fastest routes departing Taipei (TPE)

Taipei to Hong Kong latency and RTT — 15.5 ms
Taipei to Tokyo latency and RTT — 31.9 ms
Taipei to Singapore latency and RTT — 44.3 ms
Taipei to Seattle latency and RTT — 115.8 ms
Taipei to Los Angeles latency and RTT — 132 ms

Fastest routes arriving at Amsterdam (AMS)

London to Amsterdam latency and RTT — 5.2 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 — 20.3 ms

Same corridor (Asia Pacific → Europe)

Hong Kong to Moscow latency and RTT — 118.2 ms
Taipei to Moscow latency and RTT — 132.7 ms
Singapore to Marseille latency and 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. 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-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.

Taipei, Taiwan → Amsterdam, Netherlands RTT