# Singapore → Miami, USA RTT

🇸🇬 **Singapore (SIN)** → 🇺🇸 **Miami, USA (MIA)**

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

In the 2026-08-16T04:07:28Z round, ICMP echo RTT from Singapore to Miami averaged 221.7 ms across 50 samples, with a minimum of 212 ms and a maximum of 252.74 ms. Zero packet loss was recorded, and the 6.57 ms jitter figure stayed close to the standard deviation of 8.4 ms, indicating a fairly steady path during the test window.

The raw distance between the two cities is about 16,979 km, which puts a vacuum one-way floor near 113.3 ms and a glass fiber floor near 166.3 ms. This route runs 1.33 times its fiber floor, translating to roughly 75% fiber efficiency, so the observed average is within a plausible range for a long intercontinental crossing.

This path ranked 17th in the 19-route outbound set, making it one of the slower options in the group. Its spread relative to the mean is about 3.8%, slightly above the network median of 3.28%, so while latency is fair, it is not the most consistent route in the outbound set.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **221.7 ms**                                                 |
| Jitter               | **6.57 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **166.27 ms**                                                |
| Fiber Efficiency     | **75%**                                                      |
| 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 [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007) 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                      | **16,978.7 km** |
| Vacuum RTT floor                              | **113.27 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **166.27 ms**   |
| Low-latency fiber material floor              | **165.6 ms**    |
| Engineering floor (5% path allowance)         | **174.6 ms**    |
| Research 1.33× mapped-fiber reference         | **221.14 ms**   |
| Estimated unamplified path loss               | **3565.5 dB**   |
| Transparent optical spans / inline amplifiers | **223 / 222**   |
| 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        | **212 ms**    |
| Average RTT        | **221.7 ms**  |
| Maximum RTT        | **252.74 ms** |
| Standard deviation | **8.4 ms**    |
| Stdev / average    | **3.8%**      |

## Route Context

* Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* 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 Singapore latency and RTT](/docs/network/latency/pairs/mia-sin-rtt) — 223.1 ms

**Fastest routes departing Singapore (SIN)**

* [Singapore to Hong Kong latency and RTT](/docs/network/latency/pairs/sin-hkg-rtt) — 30.8 ms
* [Singapore to Taipei latency and RTT](/docs/network/latency/pairs/sin-tpe-rtt) — 45.8 ms
* [Singapore to Tokyo latency and RTT](/docs/network/latency/pairs/sin-tyo-rtt) — 68.9 ms
* [Singapore to Melbourne latency and RTT](/docs/network/latency/pairs/sin-mel-rtt) — 88.6 ms
* [Singapore to Sydney latency and RTT](/docs/network/latency/pairs/sin-syd-rtt) — 94.5 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
* [Taipei to Seattle latency and RTT](/docs/network/latency/pairs/tpe-sea-rtt) — 115.8 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/sin-mia.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → 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/sin-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.