Seattle, USA → Taipei, Taiwan RTT
ICMP RTT page for Seattle, USA to Taipei, Taiwan: 115.1 ms average, 0% packet loss, and stability data from the 2026-08-15T04:03:13Z measurement.
🇺🇸 Seattle, USA (SEA) → 🇹🇼 Taipei, Taiwan (TPE)
Measurement round: 2026-08-15T04:03:13Z.
The 2026-08-15T04:03:13Z ICMP echo RTT run from Seattle, USA to Taipei, Taiwan recorded an average of 115.1 ms across 50 samples, with a tight 111.37–122.46 ms range and zero packet loss.
Geodesic distance of 9,748.1 km puts the fiber-floor estimate at 95.46 ms, so the observed average is about 1.21 times that floor and the route runs at 82.9% fiber efficiency. That is a reasonable result for a long-haul trans-Pacific path, and the 2.99 ms standard deviation with 2.81 ms jitter indicates steady delivery.
Within the 19-route measurement set for this source, Seattle–Taipei ranks sixth by average RTT. Its standard deviation is roughly 2.6% of its average, below the network median of 3.08%, so the route offers both solid absolute latency and better-than-median relative stability.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 115.1 ms |
| Jitter | 2.81 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 95.46 ms |
| Fiber Efficiency | 82.9% |
| Latency Tier | Good |
| Source Region | North America |
| Destination Region | 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.
Ping series: SEA → TPE
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 115.1 ± 0.42 ms (SE)
Sample distribution: box = interquartile range (112.8–115.9 ms), median 114.1 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (95.5 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 111.37 |
| 2 | 100 | 112.61 |
| 3 | 200 | 111.76 |
| 4 | 300 | 112.22 |
| 5 | 400 | 117.60 |
| 6 | 500 | 115.12 |
| 7 | 600 | 120.54 |
| 8 | 700 | 115.26 |
| 9 | 800 | 119.76 |
| 10 | 900 | 114.41 |
| 11 | 1000 | 113.09 |
| 12 | 1100 | 113.07 |
| 13 | 1200 | 113.91 |
| 14 | 1300 | 120.05 |
| 15 | 1400 | 116.78 |
| 16 | 1500 | 113.82 |
| 17 | 1600 | 112.54 |
| 18 | 1700 | 115.77 |
| 19 | 1800 | 115.85 |
| 20 | 1900 | 115.32 |
| 21 | 2000 | 113.84 |
| 22 | 2100 | 115.27 |
| 23 | 2200 | 112.80 |
| 24 | 2300 | 112.56 |
| 25 | 2400 | 112.99 |
| 26 | 2500 | 121.19 |
| 27 | 2600 | 115.18 |
| 28 | 2700 | 122.46 |
| 29 | 2800 | 115.28 |
| 30 | 2900 | 113.49 |
| 31 | 3000 | 114.91 |
| 32 | 3100 | 121.17 |
| 33 | 3200 | 115.52 |
| 34 | 3300 | 112.72 |
| 35 | 3400 | 111.84 |
| 36 | 3500 | 112.47 |
| 37 | 3600 | 111.81 |
| 38 | 3700 | 121.53 |
| 39 | 3800 | 115.96 |
| 40 | 3900 | 113.45 |
| 41 | 4000 | 112.92 |
| 42 | 4100 | 113.00 |
| 43 | 4200 | 113.45 |
| 44 | 4300 | 118.86 |
| 45 | 4400 | 118.61 |
| 46 | 4500 | 119.14 |
| 47 | 4600 | 114.21 |
| 48 | 4700 | 112.83 |
| 49 | 4800 | 112.72 |
| 50 | 4900 | 111.97 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Seattle (47.60621, -122.33207) and Taipei (25.05306, 121.52639). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 9,748.1 km |
| Vacuum RTT floor | 65.03 ms |
| Standard fiber RTT floor () | 95.46 ms |
| Low-latency fiber material floor | 95.08 ms |
| Engineering floor (5% path allowance) | 100.25 ms |
| Research 1.33× mapped-fiber reference | 126.96 ms |
| Estimated unamplified path loss | 2047.1 dB |
| Transparent optical spans / inline amplifiers | 128 / 127 |
| Published RTT inflation over fiber floor | 1.21× |
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.
Stability & Trend
The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 111.37 ms |
| Average RTT | 115.1 ms |
| Maximum RTT | 122.46 ms |
| Standard deviation | 2.99 ms |
| Stdev / average | 2.6% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 115.1 ms
- Minimum
- 113.9 ms
- Maximum
- 116.0 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Seattle (SEA)
- Destination PoP: Taipei (TPE)
- Region overview: North America → Asia Pacific
- Corridor overview: North America to Asia Pacific
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Taipei to Seattle latency and RTT — 115.7 ms
Fastest routes departing Seattle (SEA)
- Seattle to Los Angeles latency and RTT — 26.6 ms
- Seattle to New York latency and RTT — 59 ms
- Seattle to Ashburn latency and RTT — 62 ms
- Seattle to Miami latency and RTT — 81.1 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
Fastest routes arriving at Taipei (TPE)
- Hong Kong to Taipei latency and RTT — 15.2 ms
- Tokyo to Taipei latency and RTT — 32.1 ms
- Singapore to Taipei latency and RTT — 44.3 ms
- Moscow to Taipei latency and RTT — 130.9 ms
- Los Angeles to Taipei latency and RTT — 131.5 ms
Same corridor (North America → Asia Pacific)
- Los Angeles to Tokyo latency and RTT — 100.9 ms
- Seattle to Hong Kong latency and RTT — 130.7 ms
- Los Angeles to Sydney latency and RTT — 139 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. Per-pair files are available at /opendata/latency/latest/pairs/sea-tpe.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Seattle → Taipei round 2026-08-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.