# Taipei, Taiwan → Miami, USA RTT

🇹🇼 **Taipei, Taiwan (TPE)** → 🇺🇸 **Miami, USA (MIA)**

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

For the 2026-08-16T04:07:28Z round, ICMP echo probes from Taipei, Taiwan, to Miami, USA, produced an average RTT of 185.7 ms, with a minimum of 175.97 ms and a maximum of 211.22 ms. No samples were lost, but jitter reached 7.6 ms and the standard deviation was 9.15 ms.

At a direct distance of 13,918.7 km, the average is about 1.36 times the fiber floor of 136.3 ms, corresponding to a 73.4% fiber efficiency and a fair latency tier rating. The route ranks 17th among the 19 routes in the measurement set.

On this route, the standard-deviation-to-average ratio is roughly 4.9%, above the 3.28% median for the 19-route set. The spread from the fastest to slowest reply was 35.25 ms, so while loss was zero, round-trip times fluctuated noticeably.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **185.7 ms**                                                 |
| Jitter               | **7.6 ms**                                                   |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **136.3 ms**                                                 |
| Fiber Efficiency     | **73.4%**                                                    |
| 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 [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **13,918.7 km** |
| Vacuum RTT floor                              | **92.86 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **136.3 ms**    |
| Low-latency fiber material floor              | **135.76 ms**   |
| Engineering floor (5% path allowance)         | **143.14 ms**   |
| Research 1.33× mapped-fiber reference         | **181.28 ms**   |
| Estimated unamplified path loss               | **2922.9 dB**   |
| Transparent optical spans / inline amplifiers | **183 / 182**   |
| Published RTT inflation over fiber floor      | **1.36×**       |

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        | **175.97 ms** |
| Average RTT        | **185.7 ms**  |
| Maximum RTT        | **211.22 ms** |
| Standard deviation | **9.15 ms**   |
| Stdev / average    | **4.9%**      |

## Route Context

* Departure PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* 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**

* [Miami to Taipei latency and RTT](/docs/network/latency/pairs/mia-tpe-rtt) — 185.1 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 Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 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-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Taipei → Miami 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-mia-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.