Miami, USA → Tokyo, Japan RTT
Miami, USA to Tokyo, Japan ICMP RTT measurement page: 50-sample round-trip latency, packet loss, jitter, and fiber-floor context.
🇺🇸 Miami, USA (MIA) → 🇯🇵 Tokyo, Japan (TYO)
Measurement round: 2026-08-15T04:03:13Z.
The 2026-08-15T04:03:13Z ICMP echo measurement from Miami, USA, to Tokyo, Japan, used 50 samples and recorded zero packet loss. Average round-trip time was 155.6 ms, with a minimum of 149.71 ms, a maximum of 180.67 ms, a standard deviation of 5.49 ms, and jitter of 4.99 ms.
The geodesic distance is approximately 12,020 km, giving a vacuum floor of 80.19 ms and a direct-fiber floor of 117.71 ms. The observed average is 1.32 times the fiber floor, a fiber efficiency of 75.6%, or an overhead of about 37.9 ms over the ideal optical path.
This route ranked 13th among the 19 outbound paths from Miami by average RTT. Its stdev-to-average ratio is about 3.5%, slightly above the route-set median near 3.1%, but the tight 5.49 ms standard deviation and sub-5 ms jitter make it a steady sample.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 155.6 ms |
| Jitter | 4.99 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 117.71 ms |
| Fiber Efficiency | 75.6% |
| Latency Tier | Fair |
| 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: MIA → TYO
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 155.6 ± 0.78 ms (SE)
Sample distribution: box = interquartile range (152.0–157.0 ms), median 154.3 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 (117.7 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 154.95 |
| 2 | 100 | 152.60 |
| 3 | 200 | 159.57 |
| 4 | 300 | 159.88 |
| 5 | 400 | 156.40 |
| 6 | 500 | 154.26 |
| 7 | 600 | 152.46 |
| 8 | 700 | 150.64 |
| 9 | 800 | 150.57 |
| 10 | 900 | 158.38 |
| 11 | 1000 | 153.18 |
| 12 | 1100 | 153.08 |
| 13 | 1200 | 150.24 |
| 14 | 1300 | 165.70 |
| 15 | 1400 | 158.63 |
| 16 | 1500 | 152.00 |
| 17 | 1600 | 157.09 |
| 18 | 1700 | 151.58 |
| 19 | 1800 | 150.75 |
| 20 | 1900 | 154.38 |
| 21 | 2000 | 154.50 |
| 22 | 2100 | 152.00 |
| 23 | 2200 | 158.00 |
| 24 | 2300 | 151.81 |
| 25 | 2400 | 160.26 |
| 26 | 2500 | 153.26 |
| 27 | 2600 | 150.24 |
| 28 | 2700 | 153.79 |
| 29 | 2800 | 171.70 |
| 30 | 2900 | 156.69 |
| 31 | 3000 | 155.71 |
| 32 | 3100 | 152.14 |
| 33 | 3200 | 156.17 |
| 34 | 3300 | 151.40 |
| 35 | 3400 | 150.93 |
| 36 | 3500 | 159.70 |
| 37 | 3600 | 155.47 |
| 38 | 3700 | 152.82 |
| 39 | 3800 | 154.14 |
| 40 | 3900 | 155.85 |
| 41 | 4000 | 155.13 |
| 42 | 4100 | 180.67 |
| 43 | 4200 | 161.46 |
| 44 | 4300 | 160.66 |
| 45 | 4400 | 156.66 |
| 46 | 4500 | 153.62 |
| 47 | 4600 | 152.10 |
| 48 | 4700 | 155.08 |
| 49 | 4800 | 151.99 |
| 50 | 4900 | 149.71 |
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 Miami (25.77427, -80.19366) and Tokyo (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 () | 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.32× |
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 | 149.71 ms |
| Average RTT | 155.6 ms |
| Maximum RTT | 180.67 ms |
| Standard deviation | 5.49 ms |
| Stdev / average | 3.5% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 155.6 ms
- Minimum
- 153.9 ms
- Maximum
- 157.2 ms
- Average loss
- 0.02%
Route Context
- Departure PoP: Miami (MIA)
- Destination PoP: Tokyo (TYO)
- 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
- Tokyo to Miami latency and RTT — 155.4 ms
Fastest routes departing Miami (MIA)
- Miami to Ashburn latency and RTT — 27.3 ms
- Miami to New York latency and RTT — 34 ms
- Miami to Los Angeles latency and RTT — 56.8 ms
- Miami to Seattle latency and RTT — 82 ms
- Miami to London latency and RTT — 100.7 ms
Fastest routes arriving at Tokyo (TYO)
- Taipei to Tokyo latency and RTT — 31.6 ms
- Hong Kong to Tokyo latency and RTT — 45 ms
- Singapore to Tokyo latency and RTT — 69.6 ms
- Seattle to Tokyo latency and RTT — 84.8 ms
- Los Angeles to Tokyo latency and RTT — 100.9 ms
Same corridor (North America → Asia Pacific)
- Seattle to Taipei latency and RTT — 115.1 ms
- Seattle to Hong Kong latency and RTT — 130.7 ms
- Los Angeles to Taipei latency and RTT — 131.5 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/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-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.