# Taipei, Taiwan → New York, USA RTT

🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **New York, USA (NYC)**

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

During the 2026-08-16T04:07:28Z round, ICMP echo requests from Taipei, Taiwan to New York, USA returned an average round-trip time of 174.2 ms, with a minimum of 165.46 ms and a maximum of 214.55 ms. None of the 50 samples were lost, and the jitter figure of 6.73 ms points to a reasonably steady path over a 12,549 km great-circle distance.

At that distance, a theoretical vacuum path would take 83.72 ms and a straight-line fiber path would take 122.89 ms. The measured average runs 1.42 times the fiber floor, or about 70.5% of theoretical fiber efficiency, putting the measured average 51.3 ms above the straight-line fiber minimum.

Compared with the 19 outbound routes measured from Taipei in this round, this path ranked 15th for RTT, meaning 14 routes were faster and 4 were slower. The typical variation from average across those outbound paths was about 3.28%, which helps frame the measured standard deviation of 8.46 ms. With 0% packet loss and 6.73 ms jitter, the route is stable despite an average that lands in the Fair latency tier.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **174.2 ms**                                                 |
| Jitter               | **6.73 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **122.89 ms**                                                |
| Fiber Efficiency     | **70.5%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific)   |
| Destination Region   | [North America](/docs/network/latency/regions/north-america) |

## 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 [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639) and [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **12,549.1 km** |
| Vacuum RTT floor                              | **83.72 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **122.89 ms**   |
| Low-latency fiber material floor              | **122.4 ms**    |
| Engineering floor (5% path allowance)         | **129.05 ms**   |
| Research 1.33× mapped-fiber reference         | **163.44 ms**   |
| Estimated unamplified path loss               | **2635.3 dB**   |
| Transparent optical spans / inline amplifiers | **165 / 164**   |
| Published RTT inflation over fiber floor      | **1.42×**       |

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        | **165.46 ms** |
| Average RTT        | **174.2 ms**  |
| Maximum RTT        | **214.55 ms** |
| Standard deviation | **8.46 ms**   |
| Stdev / average    | **4.9%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Destination PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [North America](/docs/network/latency/regions/north-america)
* 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**

* [New York to Taipei latency and RTT](/docs/network/latency/pairs/nyc-tpe-rtt) — 173.4 ms

**Fastest routes departing Taipei (TPE)**

* [Taipei to Hong Kong latency and RTT](/docs/network/latency/pairs/tpe-hkg-rtt) — 15.5 ms
* [Taipei to Tokyo latency and RTT](/docs/network/latency/pairs/tpe-tyo-rtt) — 31.9 ms
* [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms
* [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 ms
* [Taipei to Los Angeles latency and RTT](/docs/network/latency/pairs/tpe-lax-rtt) — 132 ms

**Fastest routes arriving at New York (NYC)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Los Angeles to New York latency and RTT](/docs/network/latency/pairs/lax-nyc-rtt) — 57.9 ms
* [Seattle to New York latency and RTT](/docs/network/latency/pairs/sea-nyc-rtt) — 59.5 ms
* [London to New York latency and RTT](/docs/network/latency/pairs/lon-nyc-rtt) — 63.8 ms

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

* [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
* [Hong Kong to Seattle latency and RTT](/docs/network/latency/pairs/hkg-sea-rtt) — 131.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](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tpe-nyc.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → New York 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/tpe-nyc-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.