# Miami, USA → Tokyo, Japan RTT

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

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

In the 2026-08-16T04:07:28Z measurement round, Miami-to-Tokyo ICMP echo RTT averaged 156.3 ms across 50 samples, with a minimum of 149.17 ms and a maximum of 178.72 ms. The 6.19 ms standard deviation and 4.99 ms jitter reflect a moderate spread, while 0% packet loss means all probes completed.

The direct-line distance of 12,019.9 km sets a vacuum floor of 80.19 ms and a fiber floor of 117.71 ms; the observed average is about 1.33 times the fiber floor, or 75.3% fiber efficiency. The maximum sits 22.42 ms above the average, while the minimum is only 7.13 ms below it, so the spread is more visible at the high end of the sample.

This path ranked 13th among Miami's 19 outbound routes, with 12 routes faster and 6 slower in the same round. Its standard deviation is about 3.96% of the average, above the network-wide median of 3.28% of average, which makes the upper tail worth examining even though most probes cluster near the lower end of the measured range.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **156.3 ms**                                                 |
| Jitter               | **4.99 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **117.71 ms**                                                |
| Fiber Efficiency     | **75.3%**                                                    |
| 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 [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171). 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        | **149.17 ms** |
| Average RTT        | **156.3 ms**  |
| Maximum RTT        | **178.72 ms** |
| Standard deviation | **6.19 ms**   |
| Stdev / average    | **4.0%**      |

## Route Context

* Departure PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Destination PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* 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**

* [Tokyo to Miami latency and RTT](/docs/network/latency/pairs/tyo-mia-rtt) — 156.5 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 Tokyo (TYO)**

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

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

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