# Amsterdam, Netherlands → Singapore RTT

🇳🇱 **Amsterdam, Netherlands (AMS)** → 🇸🇬 **Singapore (SIN)**

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

For the 2026-08-16T04:07:28Z measurement round, ICMP echo RTT from Amsterdam to Singapore averaged 157.6 ms, with observed values ranging from 150.92 ms to 175.59 ms. All 50 probes succeeded, and the 4.44 ms jitter points to a steady fair-latency path.

At 10,503.4 km apart, the two cities have a vacuum light-time floor of 70.07 ms and a fiber floor of 102.86 ms. The average sits 1.53 times above the fiber floor, giving a fiber efficiency of 65.3%; the extra 54.7 ms over the floor is the route's real-world distance penalty.

This Amsterdam outbound route ranks 13th among the 19 routes in the same measurement set. Its standard deviation of 6.2 ms is about 3.9% of the average, slightly above the 3.28% median variability for the set, so the route is stable but not the quietest in the set.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **157.6 ms**                                               |
| Jitter               | **4.44 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **102.86 ms**                                              |
| Fiber Efficiency     | **65.3%**                                                  |
| Latency Tier         | Fair                                                       |
| Source Region        | [Europe](/docs/network/latency/regions/europe)             |
| 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 [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969) 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                      | **10,503.4 km** |
| Vacuum RTT floor                              | **70.07 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **102.86 ms**   |
| Low-latency fiber material floor              | **102.44 ms**   |
| Engineering floor (5% path allowance)         | **108.01 ms**   |
| Research 1.33× mapped-fiber reference         | **136.8 ms**    |
| Estimated unamplified path loss               | **2205.7 dB**   |
| Transparent optical spans / inline amplifiers | **138 / 137**   |
| Published RTT inflation over fiber floor      | **1.53×**       |

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        | **150.92 ms** |
| Average RTT        | **157.6 ms**  |
| Maximum RTT        | **175.59 ms** |
| Standard deviation | **6.2 ms**    |
| Stdev / average    | **3.9%**      |

## Route Context

* Departure PoP: [Amsterdam (AMS)](/docs/network/latency/ams-amsterdam)
* Destination PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [Asia Pacific](/docs/network/latency/regions/asia-pacific)
* Corridor overview: [Europe to Asia Pacific](/docs/network/latency/regions/europe-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 Amsterdam latency and RTT](/docs/network/latency/pairs/sin-ams-rtt) — 155.8 ms

**Fastest routes departing Amsterdam (AMS)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Amsterdam to Paris latency and RTT](/docs/network/latency/pairs/ams-par-rtt) — 7 ms
* [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms
* [Amsterdam to Marseille latency and RTT](/docs/network/latency/pairs/ams-mrs-rtt) — 19.6 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 (Europe → Asia Pacific)**

* [Moscow to Hong Kong latency and RTT](/docs/network/latency/pairs/mow-hkg-rtt) — 118.6 ms
* [Moscow to Taipei latency and RTT](/docs/network/latency/pairs/mow-tpe-rtt) — 132.1 ms
* [Marseille to Singapore latency and RTT](/docs/network/latency/pairs/mrs-sin-rtt) — 139.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/ams-sin.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Amsterdam → 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/ams-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.