# Tokyo, Japan → Miami, USA RTT

🇯🇵 **Tokyo, Japan (TYO)** → 🇺🇸 **Miami, USA (MIA)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo probes from Tokyo to Miami averaged 156.5 ms, with a minimum of 154.18 ms and a maximum of 166.87 ms. All 50 samples were returned, so the measured packet loss was 0%.

The jitter was 1.73 ms and the standard deviation was 2.45 ms, giving a spread-to-average ratio of about 1.6%. Across the 19 routes from Tokyo measured in this round, Miami ranked 10th in average latency, while the median variability ratio was 3.28%; this path was more stable than that midpoint.

Tokyo is a principal East Asian exchange hub and trans-Pacific landing point, and Miami is the digital gateway between North and South America. Relative to the 12,019.9 km great-circle distance, the vacuum floor is 80.19 ms and the fiber floor is 117.71 ms; the measured average is 1.33 times that floor, or 75.2% fiber efficiency.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **156.5 ms**                                                 |
| Jitter               | **1.73 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **117.71 ms**                                                |
| Fiber Efficiency     | **75.2%**                                                    |
| 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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) 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                      | **12,019.9 km** |
| Vacuum RTT floor                              | **80.19 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **117.71 ms**   |
| Low-latency fiber material floor              | **117.24 ms**   |
| Engineering floor (5% path allowance)         | **123.61 ms**   |
| Research 1.33× mapped-fiber reference         | **156.55 ms**   |
| Estimated unamplified path loss               | **2524.2 dB**   |
| Transparent optical spans / inline amplifiers | **158 / 157**   |
| Published RTT inflation over fiber floor      | **1.33×**       |

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        | **154.18 ms** |
| Average RTT        | **156.5 ms**  |
| Maximum RTT        | **166.87 ms** |
| Standard deviation | **2.45 ms**   |
| Stdev / average    | **1.6%**      |

## Route Context

* Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* 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 Tokyo latency and RTT](/docs/network/latency/pairs/mia-tyo-rtt) — 156.3 ms

**Fastest routes departing Tokyo (TYO)**

* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [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

**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)**

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