# Singapore → Amsterdam, Netherlands RTT

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

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

In the 2026-08-16T04:07:28Z ICMP echo round, the Singapore-to-Amsterdam path averaged 155.8 ms with a minimum of 147.48 ms and a maximum of 172.04 ms; none of the 50 samples were lost.

The measured RTT is 1.51 times the 102.86 ms fiber-floor estimate for the 10,503.4 km great-circle distance, so the route converts about 66% of that theoretical minimum into actual progress. This path ranks 12th among the 19 routes measured from Singapore, and its 6.41 ms standard deviation is about 4.1% of the average, above the 3.28% median spread across that set.

Despite the slightly higher variability, the 6.07 ms jitter and zero packet loss point to a stable long-haul route; the largest measured delay was only about 16 ms above the average, so RTT stayed well contained across all 50 samples.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **155.8 ms**                                               |
| Jitter               | **6.07 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **102.86 ms**                                              |
| Fiber Efficiency     | **66%**                                                    |
| Latency Tier         | Fair                                                       |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Europe](/docs/network/latency/regions/europe)             |

## 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 [Amsterdam](https://www.geonames.org/2759794) (52.37403, 4.88969). 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.51×**       |

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        | **147.48 ms** |
| Average RTT        | **155.8 ms**  |
| Maximum RTT        | **172.04 ms** |
| Standard deviation | **6.41 ms**   |
| Stdev / average    | **4.1%**      |

## Route Context

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

* [Amsterdam to Singapore latency and RTT](/docs/network/latency/pairs/ams-sin-rtt) — 157.6 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 Amsterdam (AMS)**

* [London to Amsterdam latency and RTT](/docs/network/latency/pairs/lon-ams-rtt) — 5.2 ms
* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms
* [Paris to Amsterdam latency and RTT](/docs/network/latency/pairs/par-ams-rtt) — 7 ms
* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Marseille to Amsterdam latency and RTT](/docs/network/latency/pairs/mrs-ams-rtt) — 20.3 ms

**Same corridor (Asia Pacific → Europe)**

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