# New York, USA → Singapore RTT

🇺🇸 **New York, USA (NYC)** → 🇸🇬 **Singapore (SIN)**

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

For round 2026-08-16T04:07:28Z, 50 ICMP echo requests sent every 100 ms from New York to Singapore returned an average round-trip time of 208.7 ms, with a minimum of 197.34 ms and a maximum of 232.34 ms.

There was no packet loss, but the 8.03 ms standard deviation and 7.87 ms jitter show noticeable fluctuation across the sample. Against the theoretical fiber-floor minimum of 150.29 ms, the measured average is 1.39 times that floor, a fiber efficiency of 72 percent.

In the context of 19 outbound routes measured from New York, this route ranked 18th, placing it near the slow end of the set. Its standard-deviation-to-average ratio is about 3.8 percent, higher than the 3.28 percent median observed across those routes, so this path showed slightly more RTT variability than the typical New York outbound route in this round.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **208.7 ms**                                                 |
| Jitter               | **7.87 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **150.29 ms**                                                |
| Fiber Efficiency     | **72%**                                                      |
| 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) and [Singapore](https://www.geonames.org/1880252) (1.28967, 103.85007). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **15,347.5 km** |
| Vacuum RTT floor                              | **102.39 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **150.29 ms**   |
| Low-latency fiber material floor              | **149.69 ms**   |
| Engineering floor (5% path allowance)         | **157.83 ms**   |
| Research 1.33× mapped-fiber reference         | **199.89 ms**   |
| Estimated unamplified path loss               | **3223 dB**     |
| Transparent optical spans / inline amplifiers | **202 / 201**   |
| Published RTT inflation over fiber floor      | **1.39×**       |

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        | **197.34 ms** |
| Average RTT        | **208.7 ms**  |
| Maximum RTT        | **232.34 ms** |
| Standard deviation | **8.03 ms**   |
| Stdev / average    | **3.8%**      |

## Route Context

* Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* 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**

* [Singapore to New York latency and RTT](/docs/network/latency/pairs/sin-nyc-rtt) — 209.3 ms

**Fastest routes departing New York (NYC)**

* [New York to Ashburn latency and RTT](/docs/network/latency/pairs/nyc-iad-rtt) — 6 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [New York to Seattle latency and RTT](/docs/network/latency/pairs/nyc-sea-rtt) — 58.7 ms
* [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms
* [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms

**Fastest routes arriving at Singapore (SIN)**

* [Hong Kong to Singapore latency and RTT](/docs/network/latency/pairs/hkg-sin-rtt) — 31.5 ms
* [Taipei to Singapore latency and RTT](/docs/network/latency/pairs/tpe-sin-rtt) — 44.3 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [Melbourne to Singapore latency and RTT](/docs/network/latency/pairs/mel-sin-rtt) — 88.4 ms
* [Sydney to Singapore latency and RTT](/docs/network/latency/pairs/syd-sin-rtt) — 94.5 ms

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

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