# 🇹🇼 Taipei Ping & Network Latency (TPE) | AS203314

## 🇹🇼 Taipei (TPE)

Taipei is Taiwan's primary internet hub, providing strategic connectivity between East and Southeast Asia on Hats Network's regional backbone.

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

This page provides round-trip time (RTT) latency metrics between the **Taipei (TPE)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Taipei, Taiwan (Asia Pacific)
* **Region:** Asia Pacific
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 1668341](https://www.geonames.org/1668341) — 25.05306, 121.52639
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** TPE2
* **Upstream transit:** HE Only
* **Peering / IX:** STUIX - Taipei

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                         |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇹🇼 Taipei (TPE) → 🇭🇰 Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt) (**15.5 ms**) — Ultra-Low |
| Slowest Route         | [🇹🇼 Taipei (TPE) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tpe-jnb-rtt) (**331 ms**)           |
| Average RTT           | **152.6 ms**                                                                                                  |
| Average Jitter        | **1.24 ms**                                                                                                   |
| Average Packet Loss   | **0.06%**                                                                                                     |
| Best Fiber Efficiency | **82.4%**                                                                                                     |
| Intra-Region Peers    | 5 PoPs in Asia Pacific                                                                                        |
| Total Routes          | 19 outbound / 19 inbound (100% coverage)                                                                      |

> Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the [theoretical fiber latency methodology](/docs/network/latency/theoretical-fiber-latency).

## Geographic & Network Position

Taipei sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **15.5 ms** (Hong Kong (HKG)) to **142 ms** (Melbourne (MEL)).

Taipei sits on the East Asia corridor between Tokyo, Hong Kong and Singapore; intra-Asia systems such as APG and FASTER connect Taiwan with Japan and Hong Kong.

## Outbound Latency from Taipei (TPE)

Round-trip time in milliseconds **from Taipei** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇭🇰 Hong Kong (HKG)    | **[15.5](/docs/network/latency/pairs/tpe-hkg-rtt)**  | 7.94 ms     | 51.2%      | 0.16 ms | 0.02% | Ultra-Low |
| 🇯🇵 Tokyo (TYO)        | **[31.9](/docs/network/latency/pairs/tpe-tyo-rtt)**  | 20.58 ms    | 64.5%      | 0.23 ms | 0.08% | Excellent |
| 🇸🇬 Singapore (SIN)    | **[44.3](/docs/network/latency/pairs/tpe-sin-rtt)**  | 31.77 ms    | 71.7%      | 0.22 ms | 0.11% | Excellent |
| 🇺🇸 Seattle (SEA)      | **[115.8](/docs/network/latency/pairs/tpe-sea-rtt)** | 95.46 ms    | 82.4%      | 0.97 ms | 0.15% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[132](/docs/network/latency/pairs/tpe-lax-rtt)**   | 107 ms      | 81.1%      | 1.31 ms | 0%    | Good      |
| 🇷🇺 Moscow (MOW)       | **[132.7](/docs/network/latency/pairs/tpe-mow-rtt)** | 72.16 ms    | 54.4%      | 0.68 ms | 0.09% | Good      |
| 🇦🇺 Sydney (SYD)       | **[133.2](/docs/network/latency/pairs/tpe-syd-rtt)** | 70.88 ms    | 53.2%      | 1.48 ms | 0%    | Good      |
| 🇦🇺 Melbourne (MEL)    | **[142](/docs/network/latency/pairs/tpe-mel-rtt)**   | 72.25 ms    | 50.9%      | 1.12 ms | 0.08% | Good      |
| 🇩🇪 Berlin (BER)       | **[158.6](/docs/network/latency/pairs/tpe-ber-rtt)** | 87.84 ms    | 55.4%      | 1.84 ms | 0.09% | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[166](/docs/network/latency/pairs/tpe-fra-rtt)**   | 91.96 ms    | 55.4%      | 1.67 ms | 0.13% | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[166.5](/docs/network/latency/pairs/tpe-ams-rtt)** | 92.72 ms    | 55.7%      | 0.78 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[171.6](/docs/network/latency/pairs/tpe-iad-rtt)** | 123.78 ms   | 72.1%      | 1.7 ms  | 0%    | Fair      |
| 🇬🇧 London (LON)       | **[173](/docs/network/latency/pairs/tpe-lon-rtt)**   | 95.97 ms    | 55.5%      | 1.51 ms | 0.16% | Fair      |
| 🇫🇷 Paris (PAR)        | **[173.8](/docs/network/latency/pairs/tpe-par-rtt)** | 96.42 ms    | 55.5%      | 1.13 ms | 0.13% | Fair      |
| 🇺🇸 New York (NYC)     | **[174.2](/docs/network/latency/pairs/tpe-nyc-rtt)** | 122.89 ms   | 70.5%      | 1.24 ms | 0%    | Fair      |
| 🇫🇷 Marseille (MRS)    | **[179.5](/docs/network/latency/pairs/tpe-mrs-rtt)** | 98.2 ms     | 54.7%      | 1.4 ms  | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[185.7](/docs/network/latency/pairs/tpe-mia-rtt)** | 136.3 ms    | 73.4%      | 1.27 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[273](/docs/network/latency/pairs/tpe-gru-rtt)**   | 184.29 ms   | 67.5%      | 2.95 ms | 0.03% | High      |
| 🇿🇦 Johannesburg (JNB) | **[331](/docs/network/latency/pairs/tpe-jnb-rtt)**   | 112.87 ms   | 34.1%      | 1.92 ms | 0%    | High      |

## Fastest Routes to Taipei (TPE)

The 10 fastest measured routes **to Taipei**, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.

| Rank | Source                 | Avg RTT                                                 | Min       | Max       | Stdev   |
| ---- | ---------------------- | ------------------------------------------------------- | --------- | --------- | ------- |
| 1    | 🇭🇰 Hong Kong (HKG)   | **[14.7 ms](/docs/network/latency/pairs/hkg-tpe-rtt)**  | 13.95 ms  | 17.24 ms  | 0.72 ms |
| 2    | 🇯🇵 Tokyo (TYO)       | **[32.3 ms](/docs/network/latency/pairs/tyo-tpe-rtt)**  | 31.1 ms   | 36.28 ms  | 0.96 ms |
| 3    | 🇸🇬 Singapore (SIN)   | **[45.8 ms](/docs/network/latency/pairs/sin-tpe-rtt)**  | 43.12 ms  | 50.4 ms   | 1.72 ms |
| 4    | 🇺🇸 Seattle (SEA)     | **[114.7 ms](/docs/network/latency/pairs/sea-tpe-rtt)** | 109.75 ms | 137.83 ms | 5.07 ms |
| 5    | 🇦🇺 Sydney (SYD)      | **[131.7 ms](/docs/network/latency/pairs/syd-tpe-rtt)** | 126.36 ms | 151.94 ms | 4.46 ms |
| 6    | 🇷🇺 Moscow (MOW)      | **[132.1 ms](/docs/network/latency/pairs/mow-tpe-rtt)** | 126.75 ms | 145.67 ms | 4.52 ms |
| 7    | 🇺🇸 Los Angeles (LAX) | **[132.9 ms](/docs/network/latency/pairs/lax-tpe-rtt)** | 128.75 ms | 148.78 ms | 4.24 ms |
| 8    | 🇦🇺 Melbourne (MEL)   | **[143.2 ms](/docs/network/latency/pairs/mel-tpe-rtt)** | 135 ms    | 166.26 ms | 7.11 ms |
| 9    | 🇩🇪 Berlin (BER)      | **[156.8 ms](/docs/network/latency/pairs/ber-tpe-rtt)** | 150.23 ms | 174.22 ms | 5.07 ms |
| 10   | 🇩🇪 Frankfurt (FRA)   | **[163.8 ms](/docs/network/latency/pairs/fra-tpe-rtt)** | 159.37 ms | 176 ms    | 3.63 ms |

## Inbound Latency to Taipei (TPE)

Round-trip time in milliseconds **from all other PoPs to Taipei**. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.

| Source                  | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇭🇰 Hong Kong (HKG)    | **[14.7](/docs/network/latency/pairs/hkg-tpe-rtt)**  | 7.94 ms     | 54%        | 0.14 ms | 0.08% | Ultra-Low |
| 🇯🇵 Tokyo (TYO)        | **[32.3](/docs/network/latency/pairs/tyo-tpe-rtt)**  | 20.58 ms    | 63.7%      | 0.34 ms | 0%    | Excellent |
| 🇸🇬 Singapore (SIN)    | **[45.8](/docs/network/latency/pairs/sin-tpe-rtt)**  | 31.77 ms    | 69.4%      | 0.25 ms | 0%    | Excellent |
| 🇺🇸 Seattle (SEA)      | **[114.7](/docs/network/latency/pairs/sea-tpe-rtt)** | 95.46 ms    | 83.2%      | 1.36 ms | 0%    | Good      |
| 🇦🇺 Sydney (SYD)       | **[131.7](/docs/network/latency/pairs/syd-tpe-rtt)** | 70.88 ms    | 53.8%      | 1.51 ms | 0%    | Good      |
| 🇷🇺 Moscow (MOW)       | **[132.1](/docs/network/latency/pairs/mow-tpe-rtt)** | 72.16 ms    | 54.6%      | 1.49 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[132.9](/docs/network/latency/pairs/lax-tpe-rtt)** | 107 ms      | 80.5%      | 0.87 ms | 0.08% | Good      |
| 🇦🇺 Melbourne (MEL)    | **[143.2](/docs/network/latency/pairs/mel-tpe-rtt)** | 72.25 ms    | 50.5%      | 0.65 ms | 0%    | Good      |
| 🇩🇪 Berlin (BER)       | **[156.8](/docs/network/latency/pairs/ber-tpe-rtt)** | 87.84 ms    | 56%        | 1.45 ms | 0.17% | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[163.8](/docs/network/latency/pairs/fra-tpe-rtt)** | 91.96 ms    | 56.1%      | 1.28 ms | 0.04% | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[168.7](/docs/network/latency/pairs/ams-tpe-rtt)** | 92.72 ms    | 55%        | 1.29 ms | 0.11% | Fair      |
| 🇫🇷 Paris (PAR)        | **[171.9](/docs/network/latency/pairs/par-tpe-rtt)** | 96.42 ms    | 56.1%      | 0.85 ms | 0%    | Fair      |
| 🇺🇸 Ashburn (IAD)      | **[172.3](/docs/network/latency/pairs/iad-tpe-rtt)** | 123.78 ms   | 71.8%      | 1.59 ms | 0.04% | Fair      |
| 🇺🇸 New York (NYC)     | **[173.4](/docs/network/latency/pairs/nyc-tpe-rtt)** | 122.89 ms   | 70.9%      | 1.21 ms | 0%    | Fair      |
| 🇬🇧 London (LON)       | **[173.8](/docs/network/latency/pairs/lon-tpe-rtt)** | 95.97 ms    | 55.2%      | 1.58 ms | 0.09% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[180.9](/docs/network/latency/pairs/mrs-tpe-rtt)** | 98.2 ms     | 54.3%      | 1.86 ms | 0%    | Fair      |
| 🇺🇸 Miami (MIA)        | **[185.1](/docs/network/latency/pairs/mia-tpe-rtt)** | 136.3 ms    | 73.6%      | 1.17 ms | 0.09% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[259.1](/docs/network/latency/pairs/gru-tpe-rtt)** | 184.29 ms   | 71.1%      | 3.01 ms | 0%    | High      |
| 🇿🇦 Johannesburg (JNB) | **[329.8](/docs/network/latency/pairs/jnb-tpe-rtt)** | 112.87 ms   | 34.2%      | 3.33 ms | 0%    | High      |

## Asia Pacific Peers

Taipei is one of 6 Hats Network PoPs in **Asia Pacific**. Intra-region routes offer the lowest latency and highest path diversity.

| PoP                                     | Code | Country   | RTT (ms)  | Tier      |
| --------------------------------------- | ---- | --------- | --------- | --------- |
| [🇭🇰 Hong Kong (HKG)](./hkg-hong-kong) | HKG  | Hong Kong | **15.5**  | Ultra-Low |
| [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL  | Australia | **142**   | Good      |
| [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN  | Singapore | **44.3**  | Excellent |
| [🇦🇺 Sydney (SYD)](./syd-sydney)       | SYD  | Australia | **133.2** | Good      |
| [🇯🇵 Tokyo (TYO)](./tyo-tokyo)         | TYO  | Japan     | **31.9**  | Excellent |

## Frequently Asked Questions

**What is the fastest route to Taipei?**

The fastest measured route to Taipei (TPE) is [Hong Kong (HKG) → Taipei (TPE)](/docs/network/latency/pairs/hkg-tpe-rtt), averaging **14.7 ms** RTT (Ultra-Low).

**What is the fastest route from Taipei?**

The fastest measured route from Taipei (TPE) is [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt), averaging **15.5 ms** RTT (Ultra-Low).

**How well connected is Taipei to the Hats Network backbone?**

Taipei (TPE) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Taipei (TPE) → Johannesburg (JNB)](/docs/network/latency/pairs/tpe-jnb-rtt), averages **331 ms** RTT.

## Open Data

Measured latency data for Taipei (TPE) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) as part of the Hats Network open latency dataset:

* **Per-route files** — every directed route from Taipei is published as `tpe-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [tpe-hkg.pings.csv](/opendata/latency/latest/pairs/tpe-hkg.pings.csv), the 50-probe ICMP echo round for [Taipei (TPE) → Hong Kong (HKG)](/docs/network/latency/pairs/tpe-hkg-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/tpe-taipei).
- **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.