# Singapore → Seattle, USA RTT

🇸🇬 **Singapore (SIN)** → 🇺🇸 **Seattle, USA (SEA)**

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

For round 2026-08-16T04:07:28Z, ICMP echo RTT from Singapore to Seattle averaged 151.5 ms across 50 samples, with a minimum of 141.74 ms and a maximum of 170.28 ms. The path was loss-free, and jitter of 7.22 ms was nearly identical to the standard deviation of 7.34 ms, suggesting a steady path during the test period.

The geodesic distance of about 12,991 km corresponds to a vacuum floor of 86.67 ms and a fiber floor of 127.22 ms. At 151.5 ms, the average is 1.19 times the fiber floor, giving 84% fiber efficiency, a comparatively strong use of the physical distance between the two locations.

This route ranks 9th in the 19-route outbound set, placing it near the middle of the group. Its variability is about 4.8% of the average, above the network median of 3.28%, so while overall latency is fair and comparatively efficient, the round-trip time is not the most uniform in the set.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **151.5 ms**                                                 |
| Jitter               | **7.22 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **127.22 ms**                                                |
| Fiber Efficiency     | **84%**                                                      |
| 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 [Seattle](https://www.geonames.org/5809844) (47.60621, -122.33207). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **12,991.1 km** |
| Vacuum RTT floor                              | **86.67 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **127.22 ms**   |
| Low-latency fiber material floor              | **126.71 ms**   |
| Engineering floor (5% path allowance)         | **133.6 ms**    |
| Research 1.33× mapped-fiber reference         | **169.2 ms**    |
| Estimated unamplified path loss               | **2728.1 dB**   |
| Transparent optical spans / inline amplifiers | **171 / 170**   |
| Published RTT inflation over fiber floor      | **1.19×**       |

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        | **141.74 ms** |
| Average RTT        | **151.5 ms**  |
| Maximum RTT        | **170.28 ms** |
| Standard deviation | **7.34 ms**   |
| Stdev / average    | **4.8%**      |

## Route Context

* Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* Destination PoP: [Seattle (SEA)](/docs/network/latency/sea-seattle)
* 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**

* [Seattle to Singapore latency and RTT](/docs/network/latency/pairs/sea-sin-rtt) — 151.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 Seattle (SEA)**

* [Los Angeles to Seattle latency and RTT](/docs/network/latency/pairs/lax-sea-rtt) — 26.9 ms
* [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms
* [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms
* [Miami to Seattle latency and RTT](/docs/network/latency/pairs/mia-sea-rtt) — 81.9 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms

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

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