🇯🇵 Tokyo Ping & Network Latency (TYO) | AS203314
Tokyo (TYO) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇯🇵 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-15T04:03:13Z.
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.
Average RTT from Tokyo to every other PoP
Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round
How to read this chart
Each bar is the average round-trip time of one 50-probe ICMP echo round from Tokyo (TYO) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.
Full 19-destination dataset
| Destination | Avg RTT (ms) | Stdev (ms) | Distance (km) |
|---|---|---|---|
| Johannesburg (JNB) | 361.30 | 5.76 | 13,538 |
| São Paulo (GRU) | 229.40 | 7.68 | 18,530 |
| Marseille (MRS) | 206.70 | 6.28 | 10,113 |
| London (LON) | 204.30 | 8.36 | 9,582 |
| Paris (PAR) | 203.30 | 8.76 | 9,736 |
| Amsterdam (AMS) | 197.40 | 5.82 | 9,311 |
| Frankfurt (FRA) | 195.30 | 7.62 | 9,354 |
| Berlin (BER) | 186.40 | 7.02 | 8,938 |
| Moscow (MOW) | 162.30 | 3.99 | 7,497 |
| Miami (MIA) | 155.40 | 3.08 | 12,020 |
| New York (NYC) | 144.10 | 5.83 | 10,873 |
| Ashburn (IAD) | 143.00 | 2.83 | 10,895 |
| Melbourne (MEL) | 111.30 | 5.18 | 8,156 |
| Sydney (SYD) | 101.60 | 2.72 | 7,793 |
| Los Angeles (LAX) | 101.50 | 1.61 | 8,835 |
| Seattle (SEA) | 84.60 | 1.91 | 7,715 |
| Singapore (SIN) | 69.60 | 2.21 | 5,310 |
| Hong Kong (HKG) | 45.60 | 2.13 | 2,883 |
| Taipei (TPE) | 32.10 | 0.97 | 2,101 |
RTT vs. distance from Tokyo
Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent
How to read this chart
Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from Tokyo. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).
Underlying measurements
| Destination | Avg RTT (ms) | Distance (km) |
|---|---|---|
| Johannesburg (JNB) | 361.30 | 13,538 |
| São Paulo (GRU) | 229.40 | 18,530 |
| Marseille (MRS) | 206.70 | 10,113 |
| London (LON) | 204.30 | 9,582 |
| Paris (PAR) | 203.30 | 9,736 |
| Amsterdam (AMS) | 197.40 | 9,311 |
| Frankfurt (FRA) | 195.30 | 9,354 |
| Berlin (BER) | 186.40 | 8,938 |
| Moscow (MOW) | 162.30 | 7,497 |
| Miami (MIA) | 155.40 | 12,020 |
| New York (NYC) | 144.10 | 10,873 |
| Ashburn (IAD) | 143.00 | 10,895 |
| Melbourne (MEL) | 111.30 | 8,156 |
| Sydney (SYD) | 101.60 | 7,793 |
| Los Angeles (LAX) | 101.50 | 8,835 |
| Seattle (SEA) | 84.60 | 7,715 |
| Singapore (SIN) | 69.60 | 5,310 |
| Hong Kong (HKG) | 45.60 | 2,883 |
| Taipei (TPE) | 32.10 | 2,101 |
Fastest routes into Tokyo
Measured RTT from 19 other PoPs into Tokyo (TYO), sorted fastest first · each row spans min–max with a dot at the average
How to read this chart
Each row is one 50-probe ICMP echo round from another PoP into Tokyo (TYO): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into Tokyo can differ from the outbound path shown in the charts above.
Full 19-source dataset
| Source | Avg RTT (ms) | Min (ms) | Max (ms) | Distance (km) |
|---|---|---|---|---|
| Taipei (TPE) | 31.60 | 30.50 | 34.84 | 2,101 |
| Hong Kong (HKG) | 45.00 | 44.03 | 49.21 | 2,883 |
| Singapore (SIN) | 69.60 | 68.01 | 75.42 | 5,310 |
| Seattle (SEA) | 84.80 | 82.28 | 90.97 | 7,715 |
| Los Angeles (LAX) | 100.90 | 96.48 | 116.67 | 8,835 |
| Sydney (SYD) | 101.60 | 99.13 | 110.86 | 7,793 |
| Melbourne (MEL) | 113.20 | 110.47 | 125.36 | 8,156 |
| New York (NYC) | 142.60 | 138.01 | 151.40 | 10,873 |
| Ashburn (IAD) | 142.70 | 135.26 | 159.24 | 10,895 |
| Miami (MIA) | 155.60 | 149.71 | 180.67 | 12,020 |
| Moscow (MOW) | 162.70 | 155.66 | 186.59 | 7,497 |
| Berlin (BER) | 185.80 | 175.55 | 208.31 | 8,938 |
| Frankfurt (FRA) | 194.80 | 189.32 | 209.95 | 9,354 |
| Amsterdam (AMS) | 198.00 | 187.48 | 219.59 | 9,311 |
| London (LON) | 203.30 | 197.16 | 218.18 | 9,582 |
| Paris (PAR) | 204.20 | 198.36 | 220.26 | 9,736 |
| Marseille (MRS) | 206.00 | 198.80 | 221.27 | 10,113 |
| São Paulo (GRU) | 229.60 | 220.57 | 256.37 | 18,530 |
| Johannesburg (JNB) | 360.80 | 351.67 | 385.73 | 13,538 |
PoP Highlights
- Location: Tokyo, Japan (Asia Pacific)
- Region: Asia Pacific
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 1850147 — 35.68950, 139.69171
- Coverage: RTT measurements to 19 other PoPs across 5 continents
Facility & Interconnection
- Facility: TYO2
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇯🇵 Tokyo (TYO) → 🇹🇼 Taipei (TPE) (32.1 ms) — Excellent |
| Slowest Route | 🇯🇵 Tokyo (TYO) → 🇿🇦 Johannesburg (JNB) (361.3 ms) |
| Average RTT | 154.5 ms |
| Average Jitter | 1.21 ms |
| Average Packet Loss | 0.05% |
| Best Fiber Efficiency | 89.3% |
| 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.
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.1 ms (Taipei (TPE)) to 111.3 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.1 | 20.58 ms | 64.1% | 0.2 ms | 0.08% | Excellent |
| 🇭🇰 Hong Kong (HKG) | 45.6 | 28.24 ms | 61.9% | 0.25 ms | 0.13% | Excellent |
| 🇸🇬 Singapore (SIN) | 69.6 | 52 ms | 74.7% | 0.49 ms | 0.17% | Excellent |
| 🇺🇸 Seattle (SEA) | 84.6 | 75.55 ms | 89.3% | 0.89 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 101.5 | 86.51 ms | 85.2% | 0.67 ms | 0% | Good |
| 🇦🇺 Sydney (SYD) | 101.6 | 76.31 ms | 75.1% | 0.75 ms | 0% | Good |
| 🇦🇺 Melbourne (MEL) | 111.3 | 79.87 ms | 71.8% | 0.6 ms | 0.07% | Good |
| 🇺🇸 Ashburn (IAD) | 143 | 106.69 ms | 74.6% | 0.81 ms | 0% | Good |
| 🇺🇸 New York (NYC) | 144.1 | 106.47 ms | 73.9% | 1.3 ms | 0% | Good |
| 🇺🇸 Miami (MIA) | 155.4 | 117.71 ms | 75.7% | 0.81 ms | 0.01% | Fair |
| 🇷🇺 Moscow (MOW) | 162.3 | 73.42 ms | 45.2% | 1.1 ms | 0% | Fair |
| 🇩🇪 Berlin (BER) | 186.4 | 87.53 ms | 47% | 1.8 ms | 0.19% | Fair |
| 🇩🇪 Frankfurt (FRA) | 195.3 | 91.61 ms | 46.9% | 1.65 ms | 0% | Fair |
| 🇳🇱 Amsterdam (AMS) | 197.4 | 91.18 ms | 46.2% | 1.76 ms | 0.05% | Fair |
| 🇫🇷 Paris (PAR) | 203.3 | 95.34 ms | 46.9% | 1.5 ms | 0% | Fair |
| 🇬🇧 London (LON) | 204.3 | 93.84 ms | 45.9% | 0.96 ms | 0.06% | Fair |
| 🇫🇷 Marseille (MRS) | 206.7 | 99.03 ms | 47.9% | 2.34 ms | 0.12% | Fair |
| 🇧🇷 São Paulo (GRU) | 229.4 | 181.46 ms | 79.1% | 1.97 ms | 0% | Fair |
| 🇿🇦 Johannesburg (JNB) | 361.3 | 132.57 ms | 36.7% | 3.21 ms | 0.13% | 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.6 ms | 30.5 ms | 34.84 ms | 0.96 ms |
| 2 | 🇭🇰 Hong Kong (HKG) | 45 ms | 44.03 ms | 49.21 ms | 0.91 ms |
| 3 | 🇸🇬 Singapore (SIN) | 69.6 ms | 68.01 ms | 75.42 ms | 1.58 ms |
| 4 | 🇺🇸 Seattle (SEA) | 84.8 ms | 82.28 ms | 90.97 ms | 2.08 ms |
| 5 | 🇺🇸 Los Angeles (LAX) | 100.9 ms | 96.48 ms | 116.67 ms | 3.55 ms |
| 6 | 🇦🇺 Sydney (SYD) | 101.6 ms | 99.13 ms | 110.86 ms | 2.44 ms |
| 7 | 🇦🇺 Melbourne (MEL) | 113.2 ms | 110.47 ms | 125.36 ms | 3.06 ms |
| 8 | 🇺🇸 New York (NYC) | 142.6 ms | 138.01 ms | 151.4 ms | 3.67 ms |
| 9 | 🇺🇸 Ashburn (IAD) | 142.7 ms | 135.26 ms | 159.24 ms | 6.41 ms |
| 10 | 🇺🇸 Miami (MIA) | 155.6 ms | 149.71 ms | 180.67 ms | 5.49 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.6 | 20.58 ms | 65.1% | 0.23 ms | 0.12% | Excellent |
| 🇭🇰 Hong Kong (HKG) | 45 | 28.24 ms | 62.7% | 0.48 ms | 0.1% | Excellent |
| 🇸🇬 Singapore (SIN) | 69.6 | 52 ms | 74.7% | 0.59 ms | 0.1% | Excellent |
| 🇺🇸 Seattle (SEA) | 84.8 | 75.55 ms | 89.1% | 0.86 ms | 0.05% | Good |
| 🇺🇸 Los Angeles (LAX) | 100.9 | 86.51 ms | 85.7% | 0.68 ms | 0.08% | Good |
| 🇦🇺 Sydney (SYD) | 101.6 | 76.31 ms | 75.1% | 1.01 ms | 0% | Good |
| 🇦🇺 Melbourne (MEL) | 113.2 | 79.87 ms | 70.6% | 0.65 ms | 0% | Good |
| 🇺🇸 New York (NYC) | 142.6 | 106.47 ms | 74.7% | 0.76 ms | 0.08% | Good |
| 🇺🇸 Ashburn (IAD) | 142.7 | 106.69 ms | 74.8% | 1.6 ms | 0.13% | Good |
| 🇺🇸 Miami (MIA) | 155.6 | 117.71 ms | 75.6% | 1.57 ms | 0.07% | Fair |
| 🇷🇺 Moscow (MOW) | 162.7 | 73.42 ms | 45.1% | 1.82 ms | 0% | Fair |
| 🇩🇪 Berlin (BER) | 185.8 | 87.53 ms | 47.1% | 2.22 ms | 0% | Fair |
| 🇩🇪 Frankfurt (FRA) | 194.8 | 91.61 ms | 47% | 2.27 ms | 0% | Fair |
| 🇳🇱 Amsterdam (AMS) | 198 | 91.18 ms | 46.1% | 2 ms | 0.18% | Fair |
| 🇬🇧 London (LON) | 203.3 | 93.84 ms | 46.2% | 2.27 ms | 0.11% | Fair |
| 🇫🇷 Paris (PAR) | 204.2 | 95.34 ms | 46.7% | 2.28 ms | 0.01% | Fair |
| 🇫🇷 Marseille (MRS) | 206 | 99.03 ms | 48.1% | 0.98 ms | 0% | Fair |
| 🇧🇷 São Paulo (GRU) | 229.6 | 181.46 ms | 79% | 1.41 ms | 0.13% | Fair |
| 🇿🇦 Johannesburg (JNB) | 360.8 | 132.57 ms | 36.7% | 1.76 ms | 0.13% | 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 | 45.6 | Excellent |
| 🇦🇺 Melbourne (MEL) | MEL | Australia | 111.3 | Good |
| 🇸🇬 Singapore (SIN) | SIN | Singapore | 69.6 | Excellent |
| 🇦🇺 Sydney (SYD) | SYD | Australia | 101.6 | Good |
| 🇹🇼 Taipei (TPE) | TPE | Taiwan | 32.1 | Excellent |
Frequently Asked Questions
What is the fastest route to Tokyo?
The fastest measured route to Tokyo (TYO) is Taipei (TPE) → Tokyo (TYO), averaging 31.6 ms RTT (Excellent).
What is the fastest route from Tokyo?
The fastest measured route from Tokyo (TYO) is Tokyo (TYO) → Taipei (TPE), averaging 32.1 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), averages 361.3 ms RTT.
Open Data
Measured latency data for Tokyo (TYO) is published daily under CC 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/— for example tyo-tpe.pings.csv, the 50-probe ICMP echo round for Tokyo (TYO) → Taipei (TPE). - Dataset documentation — /opendata/latency/ covers file formats, versioning, checksums, and the aggregated full-matrix releases.
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.
🇹🇼 Taipei Ping & Network Latency (TPE) | AS203314
Taipei (TPE) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇿🇦 Johannesburg Ping & Network Latency (JNB) | AS203314
Johannesburg (JNB) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.