# Tokyo, Japan → Taipei, Taiwan RTT

🇯🇵 **Tokyo, Japan (TYO)** → 🇹🇼 **Taipei, Taiwan (TPE)**

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

For measurement round 2026-08-16T04:07:28Z, the ICMP echo RTT from Tokyo, Japan to Taipei averages 32.3 ms, with samples from 31.1 ms to 36.28 ms.

It is the fastest of the 19 outbound routes measured from Tokyo in this round. The standard deviation of 0.96 ms is about 3.0% of the average, below the 3.28% median standard-deviation-to-average ratio for the measured set; jitter is 0.75 ms and packet loss is 0%.

The observed RTT is 1.57 times the estimated fiber-floor time of 20.58 ms, a larger proportional overhead than long-haul paths, yet the absolute latency remains very low for the 2,101 km distance. Extremely low jitter and zero loss place this route at the top of the Excellent latency tier.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **32.3 ms**                                                |
| Jitter               | **0.75 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **20.58 ms**                                               |
| Fiber Efficiency     | **63.7%**                                                  |
| Latency Tier         | Excellent                                                  |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/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.

## 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](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). 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 ($n_g=1.4679$)       | **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.57×**      |

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](/docs/network/latency/theoretical-fiber-latency).

## 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        | **31.1 ms**  |
| Average RTT        | **32.3 ms**  |
| Maximum RTT        | **36.28 ms** |
| Standard deviation | **0.96 ms**  |
| Stdev / average    | **3.0%**     |

## Route Context

* Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms

**Fastest routes departing Tokyo (TYO)**

* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms
* [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms
* [Tokyo to Sydney latency and RTT](/docs/network/latency/pairs/tyo-syd-rtt) — 101.9 ms

**Fastest routes arriving at Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms
* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms

**Same corridor (Asia Pacific → Asia Pacific)**

* [Melbourne to Sydney latency and RTT](/docs/network/latency/pairs/mel-syd-rtt) — 9.8 ms
* [Sydney to Melbourne latency and RTT](/docs/network/latency/pairs/syd-mel-rtt) — 9.8 ms
* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Taipei round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-tpe-rtt).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.