# 🇯🇵 Tokyo Ping & Network Latency (TYO) | AS203314

## 🇯🇵 Tokyo (TYO)

Tokyo is East Asia's premier internet exchange hub, home to JPNAP and JPIX. Hats Network's Tokyo PoP provides ultra-low latency across the Pacific to North America.

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

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

### PoP Highlights

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

### Facility & Interconnection

* **Facility:** TYO2

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                     |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇯🇵 Tokyo (TYO) → 🇹🇼 Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-rtt) (**32.3 ms**) — Excellent |
| Slowest Route         | [🇯🇵 Tokyo (TYO) → 🇿🇦 Johannesburg (JNB)](/docs/network/latency/pairs/tyo-jnb-rtt) (**359.2 ms**)      |
| Average RTT           | **154.4 ms**                                                                                              |
| Average Jitter        | **1.25 ms**                                                                                               |
| Average Packet Loss   | **0.05%**                                                                                                 |
| Best Fiber Efficiency | **89.1%**                                                                                                 |
| 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

Tokyo sits on Hats Network's **Asia Pacific** backbone. Measured round-trip times to its 5 intra-region peers range from **32.3 ms** (Taipei (TPE)) to **113.9 ms** (Melbourne (MEL)).

Tokyo is East Asia's premier exchange hub and a landing point for trans-Pacific systems; within the region, FASTER links Japan with Taiwan.

## Outbound Latency from Tokyo (TYO)

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

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇹🇼 Taipei (TPE)       | **[32.3](/docs/network/latency/pairs/tyo-tpe-rtt)**  | 20.58 ms    | 63.7%      | 0.34 ms | 0%    | Excellent |
| 🇭🇰 Hong Kong (HKG)    | **[44.8](/docs/network/latency/pairs/tyo-hkg-rtt)**  | 28.24 ms    | 63%        | 0.45 ms | 0.07% | Excellent |
| 🇸🇬 Singapore (SIN)    | **[69.4](/docs/network/latency/pairs/tyo-sin-rtt)**  | 52 ms       | 74.9%      | 0.62 ms | 0%    | Excellent |
| 🇺🇸 Seattle (SEA)      | **[84.8](/docs/network/latency/pairs/tyo-sea-rtt)**  | 75.55 ms    | 89.1%      | 0.77 ms | 0.06% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[101.2](/docs/network/latency/pairs/tyo-lax-rtt)** | 86.51 ms    | 85.5%      | 0.97 ms | 0.02% | Good      |
| 🇦🇺 Sydney (SYD)       | **[101.9](/docs/network/latency/pairs/tyo-syd-rtt)** | 76.31 ms    | 74.9%      | 0.92 ms | 0.2%  | Good      |
| 🇦🇺 Melbourne (MEL)    | **[113.9](/docs/network/latency/pairs/tyo-mel-rtt)** | 79.87 ms    | 70.1%      | 1.25 ms | 0.05% | Good      |
| 🇺🇸 Ashburn (IAD)      | **[142.9](/docs/network/latency/pairs/tyo-iad-rtt)** | 106.69 ms   | 74.7%      | 0.69 ms | 0%    | Good      |
| 🇺🇸 New York (NYC)     | **[144.6](/docs/network/latency/pairs/tyo-nyc-rtt)** | 106.47 ms   | 73.6%      | 1.33 ms | 0.17% | Good      |
| 🇺🇸 Miami (MIA)        | **[156.5](/docs/network/latency/pairs/tyo-mia-rtt)** | 117.71 ms   | 75.2%      | 1.36 ms | 0.14% | Fair      |
| 🇷🇺 Moscow (MOW)       | **[161.7](/docs/network/latency/pairs/tyo-mow-rtt)** | 73.42 ms    | 45.4%      | 1.62 ms | 0.09% | Fair      |
| 🇩🇪 Berlin (BER)       | **[186.1](/docs/network/latency/pairs/tyo-ber-rtt)** | 87.53 ms    | 47%        | 1.64 ms | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[193.2](/docs/network/latency/pairs/tyo-fra-rtt)** | 91.61 ms    | 47.4%      | 2.16 ms | 0%    | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[197.4](/docs/network/latency/pairs/tyo-ams-rtt)** | 91.18 ms    | 46.2%      | 1.09 ms | 0%    | Fair      |
| 🇬🇧 London (LON)       | **[202.7](/docs/network/latency/pairs/tyo-lon-rtt)** | 93.84 ms    | 46.3%      | 0.93 ms | 0%    | Fair      |
| 🇫🇷 Paris (PAR)        | **[204.8](/docs/network/latency/pairs/tyo-par-rtt)** | 95.34 ms    | 46.6%      | 2.06 ms | 0.03% | Fair      |
| 🇫🇷 Marseille (MRS)    | **[205.6](/docs/network/latency/pairs/tyo-mrs-rtt)** | 99.03 ms    | 48.2%      | 1.86 ms | 0.14% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[230.5](/docs/network/latency/pairs/tyo-gru-rtt)** | 181.46 ms   | 78.7%      | 1.53 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[359.2](/docs/network/latency/pairs/tyo-jnb-rtt)** | 132.57 ms   | 36.9%      | 2.19 ms | 0.05% | High      |

## Fastest Routes to Tokyo (TYO)

The 10 fastest measured routes **to Tokyo**, 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    | 🇹🇼 Taipei (TPE)      | **[31.9 ms](/docs/network/latency/pairs/tpe-tyo-rtt)**  | 30.57 ms  | 35.67 ms  | 1.12 ms |
| 2    | 🇭🇰 Hong Kong (HKG)   | **[44.9 ms](/docs/network/latency/pairs/hkg-tyo-rtt)**  | 42.32 ms  | 50.91 ms  | 1.82 ms |
| 3    | 🇸🇬 Singapore (SIN)   | **[68.9 ms](/docs/network/latency/pairs/sin-tyo-rtt)**  | 65.47 ms  | 78.16 ms  | 2.72 ms |
| 4    | 🇺🇸 Seattle (SEA)     | **[85 ms](/docs/network/latency/pairs/sea-tyo-rtt)**    | 81.03 ms  | 97.43 ms  | 3.15 ms |
| 5    | 🇺🇸 Los Angeles (LAX) | **[101.2 ms](/docs/network/latency/pairs/lax-tyo-rtt)** | 97.1 ms   | 112.57 ms | 3.72 ms |
| 6    | 🇦🇺 Sydney (SYD)      | **[101.3 ms](/docs/network/latency/pairs/syd-tyo-rtt)** | 99.25 ms  | 108.62 ms | 2.05 ms |
| 7    | 🇦🇺 Melbourne (MEL)   | **[112 ms](/docs/network/latency/pairs/mel-tyo-rtt)**   | 105.34 ms | 140.34 ms | 5.58 ms |
| 8    | 🇺🇸 Ashburn (IAD)     | **[141.9 ms](/docs/network/latency/pairs/iad-tyo-rtt)** | 136.1 ms  | 154.55 ms | 4.32 ms |
| 9    | 🇺🇸 New York (NYC)    | **[143.1 ms](/docs/network/latency/pairs/nyc-tyo-rtt)** | 136.69 ms | 171.34 ms | 6.58 ms |
| 10   | 🇺🇸 Miami (MIA)       | **[156.3 ms](/docs/network/latency/pairs/mia-tyo-rtt)** | 149.17 ms | 178.72 ms | 6.19 ms |

## Inbound Latency to Tokyo (TYO)

Round-trip time in milliseconds **from all other PoPs to Tokyo**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇹🇼 Taipei (TPE)       | **[31.9](/docs/network/latency/pairs/tpe-tyo-rtt)**  | 20.58 ms    | 64.5%      | 0.23 ms | 0.08% | Excellent |
| 🇭🇰 Hong Kong (HKG)    | **[44.9](/docs/network/latency/pairs/hkg-tyo-rtt)**  | 28.24 ms    | 62.9%      | 0.23 ms | 0.08% | Excellent |
| 🇸🇬 Singapore (SIN)    | **[68.9](/docs/network/latency/pairs/sin-tyo-rtt)**  | 52 ms       | 75.5%      | 0.41 ms | 0%    | Excellent |
| 🇺🇸 Seattle (SEA)      | **[85](/docs/network/latency/pairs/sea-tyo-rtt)**    | 75.55 ms    | 88.9%      | 0.39 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[101.2](/docs/network/latency/pairs/lax-tyo-rtt)** | 86.51 ms    | 85.5%      | 0.82 ms | 0%    | Good      |
| 🇦🇺 Sydney (SYD)       | **[101.3](/docs/network/latency/pairs/syd-tyo-rtt)** | 76.31 ms    | 75.3%      | 0.74 ms | 0%    | Good      |
| 🇦🇺 Melbourne (MEL)    | **[112](/docs/network/latency/pairs/mel-tyo-rtt)**   | 79.87 ms    | 71.3%      | 0.86 ms | 0%    | Good      |
| 🇺🇸 Ashburn (IAD)      | **[141.9](/docs/network/latency/pairs/iad-tyo-rtt)** | 106.69 ms   | 75.2%      | 1.23 ms | 0.02% | Good      |
| 🇺🇸 New York (NYC)     | **[143.1](/docs/network/latency/pairs/nyc-tyo-rtt)** | 106.47 ms   | 74.4%      | 0.8 ms  | 0%    | Good      |
| 🇺🇸 Miami (MIA)        | **[156.3](/docs/network/latency/pairs/mia-tyo-rtt)** | 117.71 ms   | 75.3%      | 0.95 ms | 0.03% | Fair      |
| 🇷🇺 Moscow (MOW)       | **[162.2](/docs/network/latency/pairs/mow-tyo-rtt)** | 73.42 ms    | 45.3%      | 1.92 ms | 0.08% | Fair      |
| 🇩🇪 Berlin (BER)       | **[187.5](/docs/network/latency/pairs/ber-tyo-rtt)** | 87.53 ms    | 46.7%      | 1.21 ms | 0%    | Fair      |
| 🇩🇪 Frankfurt (FRA)    | **[194.5](/docs/network/latency/pairs/fra-tyo-rtt)** | 91.61 ms    | 47.1%      | 1.29 ms | 0.12% | Fair      |
| 🇳🇱 Amsterdam (AMS)    | **[198.2](/docs/network/latency/pairs/ams-tyo-rtt)** | 91.18 ms    | 46%        | 1.27 ms | 0.14% | Fair      |
| 🇬🇧 London (LON)       | **[202.9](/docs/network/latency/pairs/lon-tyo-rtt)** | 93.84 ms    | 46.2%      | 1.61 ms | 0%    | Fair      |
| 🇫🇷 Marseille (MRS)    | **[203.8](/docs/network/latency/pairs/mrs-tyo-rtt)** | 99.03 ms    | 48.6%      | 2.03 ms | 0.18% | Fair      |
| 🇫🇷 Paris (PAR)        | **[204.7](/docs/network/latency/pairs/par-tyo-rtt)** | 95.34 ms    | 46.6%      | 2.17 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[230.3](/docs/network/latency/pairs/gru-tyo-rtt)** | 181.46 ms   | 78.8%      | 2.42 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[360.5](/docs/network/latency/pairs/jnb-tyo-rtt)** | 132.57 ms   | 36.8%      | 2.79 ms | 0.06% | High      |

## Asia Pacific Peers

Tokyo 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 | **44.8**  | Excellent |
| [🇦🇺 Melbourne (MEL)](./mel-melbourne) | MEL  | Australia | **113.9** | Good      |
| [🇸🇬 Singapore (SIN)](./sin-singapore) | SIN  | Singapore | **69.4**  | Excellent |
| [🇦🇺 Sydney (SYD)](./syd-sydney)       | SYD  | Australia | **101.9** | Good      |
| [🇹🇼 Taipei (TPE)](./tpe-taipei)       | TPE  | Taiwan    | **32.3**  | Excellent |

## Frequently Asked Questions

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

The fastest measured route to Tokyo (TYO) is [Taipei (TPE) → Tokyo (TYO)](/docs/network/latency/pairs/tpe-tyo-rtt), averaging **31.9 ms** RTT (Excellent).

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

The fastest measured route from Tokyo (TYO) is [Tokyo (TYO) → Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-rtt), averaging **32.3 ms** RTT (Excellent).

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

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

## Open Data

Measured latency data for Tokyo (TYO) 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 Tokyo is published as `tyo-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [tyo-tpe.pings.csv](/opendata/latency/latest/pairs/tyo-tpe.pings.csv), the 50-probe ICMP echo round for [Tokyo (TYO) → Taipei (TPE)](/docs/network/latency/pairs/tyo-tpe-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/tyo-tokyo).
- **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.