Singapore → Amsterdam, Netherlands RTT
Live ICMP RTT data from Singapore to Amsterdam, Netherlands: average latency, jitter, packet loss and route efficiency for the 2026-08-15T04:03:13Z round.
🇸🇬 Singapore (SIN) → 🇳🇱 Amsterdam, Netherlands (AMS)
Measurement round: 2026-08-15T04:03:13Z.
Singapore to Amsterdam recorded a 157.3 ms average ICMP RTT in measurement round 2026-08-15T04:03:13Z, based on 50 samples taken at 100 ms intervals. The minimum was 149.78 ms, the maximum was 176.63 ms, jitter was 5.98 ms, and packet loss was 0%, so the link stayed fully available during the test window.
The observed average sits 1.53 times above the theoretical fiber floor for 10,503 km, giving a fiber efficiency of 65.4%. In practical terms, the route carries a noticeable latency overhead beyond the straight-line cable distance, and the average RTT should be treated as the expected operational latency rather than an ideal-case value.
Among the 19 routes leaving this Singapore origin, the route ranks 11th by average RTT. Its 7.49 ms standard deviation is about 4.8% of the average, higher than the network median of 3.08%, and the 26.85 ms gap between minimum and maximum means traffic engineers should plan for a wider latency envelope than the average alone suggests.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 157.3 ms |
| Jitter | 5.98 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 102.86 ms |
| Fiber Efficiency | 65.4% |
| Latency Tier | Fair |
| Source Region | Asia Pacific |
| Destination Region | 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.
Ping series: SIN → AMS
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 157.3 ± 1.06 ms (SE)
Sample distribution: box = interquartile range (151.6–160.0 ms), median 155.2 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.
How to read this chart
The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.
The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (102.9 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 155.13 |
| 2 | 100 | 152.04 |
| 3 | 200 | 151.62 |
| 4 | 300 | 155.61 |
| 5 | 400 | 173.92 |
| 6 | 500 | 158.32 |
| 7 | 600 | 172.56 |
| 8 | 700 | 166.11 |
| 9 | 800 | 156.03 |
| 10 | 900 | 161.78 |
| 11 | 1000 | 155.54 |
| 12 | 1100 | 151.53 |
| 13 | 1200 | 151.36 |
| 14 | 1300 | 152.39 |
| 15 | 1400 | 160.32 |
| 16 | 1500 | 176.63 |
| 17 | 1600 | 159.44 |
| 18 | 1700 | 155.38 |
| 19 | 1800 | 166.12 |
| 20 | 1900 | 155.29 |
| 21 | 2000 | 151.43 |
| 22 | 2100 | 152.79 |
| 23 | 2200 | 151.20 |
| 24 | 2300 | 152.97 |
| 25 | 2400 | 156.39 |
| 26 | 2500 | 154.54 |
| 27 | 2600 | 151.62 |
| 28 | 2700 | 155.70 |
| 29 | 2800 | 151.65 |
| 30 | 2900 | 150.24 |
| 31 | 3000 | 151.55 |
| 32 | 3100 | 150.25 |
| 33 | 3200 | 149.78 |
| 34 | 3300 | 150.43 |
| 35 | 3400 | 149.79 |
| 36 | 3500 | 160.38 |
| 37 | 3600 | 176.63 |
| 38 | 3700 | 159.40 |
| 39 | 3800 | 154.90 |
| 40 | 3900 | 173.98 |
| 41 | 4000 | 173.45 |
| 42 | 4100 | 161.54 |
| 43 | 4200 | 153.64 |
| 44 | 4300 | 160.22 |
| 45 | 4400 | 157.40 |
| 46 | 4500 | 156.80 |
| 47 | 4600 | 154.21 |
| 48 | 4700 | 151.09 |
| 49 | 4800 | 150.90 |
| 50 | 4900 | 153.01 |
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 for citation guidance.
Download this dataset
Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for Singapore (1.28967, 103.85007) and Amsterdam (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 () | 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.
Stability & Trend
The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 149.78 ms |
| Average RTT | 157.3 ms |
| Maximum RTT | 176.63 ms |
| Standard deviation | 7.49 ms |
| Stdev / average | 4.8% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 157.3 ms
- Minimum
- 155.5 ms
- Maximum
- 158.9 ms
- Average loss
- 0.01%
Route Context
- Departure PoP: Singapore (SIN)
- Destination PoP: Amsterdam (AMS)
- Region overview: Asia Pacific → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- Amsterdam to Singapore latency and RTT — 158.2 ms
Fastest routes departing Singapore (SIN)
- Singapore to Hong Kong latency and RTT — 30.9 ms
- Singapore to Taipei latency and RTT — 44.3 ms
- Singapore to Tokyo latency and RTT — 69.6 ms
- Singapore to Melbourne latency and RTT — 87.8 ms
- Singapore to Sydney latency and RTT — 95.3 ms
Fastest routes arriving at Amsterdam (AMS)
- London to Amsterdam latency and RTT — 5.1 ms
- Frankfurt to Amsterdam latency and RTT — 5.9 ms
- Paris to Amsterdam latency and RTT — 7 ms
- Berlin to Amsterdam latency and RTT — 7.2 ms
- Marseille to Amsterdam latency and RTT — 19.6 ms
Same corridor (Asia Pacific → Europe)
- Hong Kong to Moscow latency and RTT — 116.6 ms
- Taipei to Moscow latency and RTT — 131.7 ms
- Singapore to Marseille latency and RTT — 138.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. 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-15T04:03:13Z, CC BY 4.0".
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.