Tokyo, Japan to Amsterdam, Netherlands: ICMP RTT measurement results with average latency, jitter, packet loss, and route distance.

🇯🇵 Tokyo, Japan (TYO) → 🇳🇱 Amsterdam, Netherlands (AMS)

Measurement round: 2026-08-15T04:03:13Z.

In the 2026-08-15T04:03:13Z round, 50 ICMP echo probes from Tokyo to Amsterdam averaged 197.4 ms, with the fastest sample at 191.06 ms and the slowest at 217.26 ms. Packet loss was 0%, while the standard deviation of 5.82 ms and jitter of 5.46 ms describe a steady, tightly grouped path.

The great-circle distance of 9,311.4 km yields a theoretical vacuum floor of 62.12 ms and a fiber floor of 91.18 ms. The observed average sits 2.16 times above the fiber floor, equal to 46.2% fiber efficiency, which explains the Fair latency tier and leaves meaningful headroom between the real-world RTT and the physical distance minimum.

Among the 19 outbound routes in the same round, this route ranked 14th by average RTT, so it was slower on the whole. Its standard deviation is roughly 2.9% of its average, slightly better than the network-wide median variation of 3.08%, meaning consistent timing—not speed—is the route's stronger attribute.

Latency Summary

Metric	Value
RTT	197.4 ms
Jitter	5.46 ms
Packet Loss	0%
Standard Fiber Floor	91.18 ms
Fiber Efficiency	46.2%
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: TYO → AMS

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 197.4 ± 0.82 ms (SE)

Sample distribution: box = interquartile range (193.3–199.5 ms), median 195.4 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 (91.2 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	193.27
2	100	217.26
3	200	199.52
4	300	213.32
5	400	207.06
6	500	198.77
7	600	195.95
8	700	192.39
9	800	200.59
10	900	194.53
11	1000	192.91
12	1100	194.10
13	1200	191.34
14	1300	198.33
15	1400	194.87
16	1500	207.20
17	1600	196.83
18	1700	194.62
19	1800	192.42
20	1900	200.23
21	2000	200.26
22	2100	193.69
23	2200	191.33
24	2300	197.41
25	2400	194.08
26	2500	192.33
27	2600	194.77
28	2700	193.41
29	2800	202.57
30	2900	198.11
31	3000	192.81
32	3100	197.69
33	3200	195.42
34	3300	191.90
35	3400	191.06
36	3500	195.41
37	3600	200.86
38	3700	197.10
39	3800	195.43
40	3900	192.03
41	4000	191.82
42	4100	194.73
43	4200	213.78
44	4300	202.08
45	4400	194.06
46	4500	192.59
47	4600	198.73
48	4700	199.35
49	4800	198.71
50	4900	200.97

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 Tokyo (35.68950, 139.69171) and Amsterdam (52.37403, 4.88969). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	9,311.4 km
Vacuum RTT floor	62.12 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	91.18 ms
Low-latency fiber material floor	90.82 ms
Engineering floor (5% path allowance)	95.76 ms
Research 1.33× mapped-fiber reference	121.28 ms
Estimated unamplified path loss	1955.4 dB
Transparent optical spans / inline amplifiers	123 / 122
Published RTT inflation over fiber floor	2.16×

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	191.06 ms
Average RTT	197.4 ms
Maximum RTT	217.26 ms
Standard deviation	5.82 ms
Stdev / average	2.9%

RTT trend

Estimated route stability across the selected time window.

Average: 197.4 ms
Minimum: 195.6 ms
Maximum: 199.4 ms
Average loss: 0.03%

Route Context

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

Reverse direction

Amsterdam to Tokyo latency and RTT — 198 ms

Fastest routes departing Tokyo (TYO)

Tokyo to Taipei latency and RTT — 32.1 ms
Tokyo to Hong Kong latency and RTT — 45.6 ms
Tokyo to Singapore latency and RTT — 69.6 ms
Tokyo to Seattle latency and RTT — 84.6 ms
Tokyo to Los Angeles latency and RTT — 101.5 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
Taipei to Moscow latency and RTT — 131.7 ms
Singapore to Marseille latency and RTT — 138.8 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/tyo-ams.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → 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.

Tokyo, Japan → Amsterdam, Netherlands RTT