# Miami, USA → Taipei, Taiwan RTT

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

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Miami, USA to Taipei, Taiwan averaged 185.1 ms over 50 samples, with a minimum of 178.34 ms and a maximum of 197.2 ms. The 5.13 ms standard deviation and 4.64 ms jitter indicate a tightly grouped result, and all 50 echoes were answered.

At a geodesic distance of 13,918.7 km, the vacuum floor is 92.86 ms and the fiber floor is 136.3 ms; the measured mean sits about 1.36 times the fiber floor, corresponding to 73.6% fiber efficiency. The narrow min-to-max range of 18.86 ms shows that the overhead is fairly consistent across every sample rather than driven by occasional outliers.

Ranked 14th among Miami's 19 outbound routes, Taipei's average RTT was slower than 13 of those routes and faster than 5. Its standard deviation is roughly 2.77% of the average, below the network-wide median of 3.28% of average, so the route's stability is actually better than the typical outbound path despite the higher average latency.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **185.1 ms**                                                 |
| Jitter               | **4.64 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **136.3 ms**                                                 |
| Fiber Efficiency     | **73.6%**                                                    |
| Latency Tier         | Fair                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| Destination Region   | [Asia Pacific](/docs/network/latency/regions/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.

## 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 [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366) and [Taipei](https://www.geonames.org/1668341) (25.05306, 121.52639). 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        | **178.34 ms** |
| Average RTT        | **185.1 ms**  |
| Maximum RTT        | **197.2 ms**  |
| Standard deviation | **5.13 ms**   |
| Stdev / average    | **2.8%**      |

## Route Context

* Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Destination PoP: [Taipei (TPE)](/docs/network/latency/tpe-taipei)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [North America to Asia Pacific](/docs/network/latency/regions/north-america-to-asia-pacific)
* 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**

* [Taipei to Miami latency and RTT](/docs/network/latency/pairs/tpe-mia-rtt) — 185.7 ms

**Fastest routes departing Miami (MIA)**

* [Miami to Ashburn latency and RTT](/docs/network/latency/pairs/mia-iad-rtt) — 27.3 ms
* [Miami to New York latency and RTT](/docs/network/latency/pairs/mia-nyc-rtt) — 33.3 ms
* [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms
* [Miami to London latency and RTT](/docs/network/latency/pairs/mia-lon-rtt) — 101.8 ms

**Fastest routes arriving at Taipei (TPE)**

* [Hong Kong to Taipei latency and RTT](/docs/network/latency/pairs/hkg-tpe-rtt) — 14.7 ms
* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Seattle to Taipei latency and RTT](/docs/network/latency/pairs/sea-tpe-rtt) — 114.7 ms
* [Sydney to Taipei latency and RTT](/docs/network/latency/pairs/syd-tpe-rtt) — 131.7 ms

**Same corridor (North America → Asia Pacific)**

* [Seattle to Tokyo latency and RTT](/docs/network/latency/pairs/sea-tyo-rtt) — 85 ms
* [Los Angeles to Tokyo latency and RTT](/docs/network/latency/pairs/lax-tyo-rtt) — 101.2 ms
* [Seattle to Hong Kong latency and RTT](/docs/network/latency/pairs/sea-hkg-rtt) — 130.4 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/mia-tpe.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Taipei 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/mia-tpe-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.