Taipei, Taiwan → Tokyo, Japan RTT
Measured ICMP round-trip time between Taipei, Taiwan and Tokyo, Japan: 31.9 ms average latency, 0% packet loss, 1.06 ms jitter across 50 samples.
🇹🇼 Taipei, Taiwan (TPE) → 🇯🇵 Tokyo, Japan (TYO)
Measurement round: 2026-08-16T04:07:28Z.
The Taipei–Tokyo ICMP echo run from round 2026-08-16T04:07:28Z returned a 31.9 ms average RTT, with a minimum of 30.57 ms, a maximum of 35.67 ms, and 1.06 ms jitter over 50 samples. No packets were lost, and the measured latency tier was Excellent.
Across the 19 outbound routes in this round, Taipei–Tokyo ranked second by average latency. The route's standard deviation was 1.12 ms, or 3.51% of the mean, slightly above the 3.28% median variability for the measured outbound set; it is very fast, with a bit more packet-level spread than its speed rank might suggest.
At 2,101.2 km, the observed mean is 1.55 times the 20.58 ms fiber-floor estimate, giving a 64.5% fiber efficiency. The result aligns with Tokyo's role as East Asia's premier exchange hub and makes this short intra-Asia hop one of the strongest round-trip profiles in the round.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 31.9 ms |
| Jitter | 1.06 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 20.58 ms |
| Fiber Efficiency | 64.5% |
| Latency Tier | Excellent |
| Source Region | Asia Pacific |
| 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: TPE → TYO
50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 31.9 ± 0.16 ms (SE)
Sample distribution: box = interquartile range (31.2–32.2 ms), median 31.6 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 (20.6 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 31.17 |
| 2 | 100 | 32.19 |
| 3 | 200 | 32.05 |
| 4 | 300 | 31.82 |
| 5 | 400 | 31.40 |
| 6 | 500 | 31.31 |
| 7 | 600 | 31.81 |
| 8 | 700 | 34.73 |
| 9 | 800 | 32.38 |
| 10 | 900 | 33.15 |
| 11 | 1000 | 32.48 |
| 12 | 1100 | 31.33 |
| 13 | 1200 | 30.99 |
| 14 | 1300 | 32.51 |
| 15 | 1400 | 32.76 |
| 16 | 1500 | 31.21 |
| 17 | 1600 | 32.02 |
| 18 | 1700 | 31.64 |
| 19 | 1800 | 30.92 |
| 20 | 1900 | 30.65 |
| 21 | 2000 | 35.36 |
| 22 | 2100 | 32.61 |
| 23 | 2200 | 31.63 |
| 24 | 2300 | 31.40 |
| 25 | 2400 | 30.69 |
| 26 | 2500 | 32.20 |
| 27 | 2600 | 31.24 |
| 28 | 2700 | 31.91 |
| 29 | 2800 | 31.05 |
| 30 | 2900 | 30.57 |
| 31 | 3000 | 30.57 |
| 32 | 3100 | 31.35 |
| 33 | 3200 | 32.23 |
| 34 | 3300 | 31.85 |
| 35 | 3400 | 30.88 |
| 36 | 3500 | 31.62 |
| 37 | 3600 | 33.92 |
| 38 | 3700 | 31.89 |
| 39 | 3800 | 31.01 |
| 40 | 3900 | 30.88 |
| 41 | 4000 | 30.82 |
| 42 | 4100 | 32.37 |
| 43 | 4200 | 31.66 |
| 44 | 4300 | 35.67 |
| 45 | 4400 | 33.34 |
| 46 | 4500 | 31.88 |
| 47 | 4600 | 31.09 |
| 48 | 4700 | 31.43 |
| 49 | 4800 | 32.20 |
| 50 | 4900 | 31.16 |
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 Tokyo (35.68950, 139.69171). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 2,101.2 km |
| Vacuum RTT floor | 14.02 ms |
| Standard fiber RTT floor () | 20.58 ms |
| Low-latency fiber material floor | 20.49 ms |
| Engineering floor (5% path allowance) | 21.61 ms |
| Research 1.33× mapped-fiber reference | 27.37 ms |
| Estimated unamplified path loss | 441.3 dB |
| Transparent optical spans / inline amplifiers | 28 / 27 |
| Published RTT inflation over fiber floor | 1.55× |
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 | 30.57 ms |
| Average RTT | 31.9 ms |
| Maximum RTT | 35.67 ms |
| Standard deviation | 1.12 ms |
| Stdev / average | 3.5% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 31.9 ms
- Minimum
- 31.6 ms
- Maximum
- 32.2 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Taipei (TPE)
- Destination PoP: Tokyo (TYO)
- Region overview: Asia Pacific → Asia Pacific
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Tokyo to Taipei latency and RTT — 32.3 ms
Fastest routes departing Taipei (TPE)
- Taipei to Hong Kong latency and RTT — 15.5 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
- Taipei to Moscow latency and RTT — 132.7 ms
Fastest routes arriving at Tokyo (TYO)
- Hong Kong to Tokyo latency and RTT — 44.9 ms
- Singapore to Tokyo latency and RTT — 68.9 ms
- Seattle to Tokyo latency and RTT — 85 ms
- Los Angeles to Tokyo latency and RTT — 101.2 ms
- Sydney to Tokyo latency and RTT — 101.3 ms
Same corridor (Asia Pacific → Asia Pacific)
- Melbourne to Sydney latency and RTT — 9.8 ms
- Sydney to Melbourne latency and RTT — 9.8 ms
- Hong Kong to Taipei latency and RTT — 14.7 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-tyo.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Tokyo 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.