# Singapore → London, UK RTT

🇸🇬 &#x2A;*Singapore (SIN)** → 🇬🇧 &#x2A;*London, UK (LON)**

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

During the 2026-08-16T04:07:28Z measurement round, ICMP echo requests sent from Singapore to London, UK, produced an average round-trip time of 155.4 ms, with a minimum of 150.37 ms, a maximum of 180.35 ms, and no packet loss across all 50 samples. The standard deviation was 5.16 ms and jitter was 3.28 ms, so the route maintained a fairly narrow, repeatable RTT profile.

The straight-line separation of 10,859.7 km yields an ideal fiber-only floor of about 106.35 ms. The measured average is 1.46 times that floor, which puts distance-adjusted efficiency at 68.4%; roughly 49 ms of overhead is added beyond the theoretical minimum for this route.

Across the 19 outbound routes measured from Singapore in the same round, this route ranked 11th by average RTT. Its observed variation of 5.16 ms is a slightly larger share of the mean than the network-wide median ratio of 3.28%, meaning the occasional 180 ms samples are less typical; most probes sit near the low-150s portion of the range.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **155.4 ms**                                               |
| Jitter               | **3.28 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **106.35 ms**                                              |
| Fiber Efficiency     | **68.4%**                                                  |
| 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 [London](https://www.geonames.org/2643743) (51.50853, -0.12574). It does not disclose either facility address.

| Physical Reference                            | Value           |
| --------------------------------------------- | --------------- |
| WGS-84 geodesic distance                      | **10,859.7 km** |
| Vacuum RTT floor                              | **72.45 ms**    |
| Standard fiber RTT floor ($n_g=1.4679$)       | **106.35 ms**   |
| Low-latency fiber material floor              | **105.92 ms**   |
| Engineering floor (5% path allowance)         | **111.68 ms**   |
| Research 1.33× mapped-fiber reference         | **141.44 ms**   |
| Estimated unamplified path loss               | **2280.5 dB**   |
| Transparent optical spans / inline amplifiers | **143 / 142**   |
| Published RTT inflation over fiber floor      | **1.46×**       |

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.37 ms** |
| Average RTT        | **155.4 ms**  |
| Maximum RTT        | **180.35 ms** |
| Standard deviation | **5.16 ms**   |
| Stdev / average    | **3.3%**      |

## Route Context

* Departure PoP: [Singapore (SIN)](/docs/network/latency/sin-singapore)
* Destination PoP: [London (LON)](/docs/network/latency/lon-london)
* 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**

* [London to Singapore latency and RTT](/docs/network/latency/pairs/lon-sin-rtt) — 156.5 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 London (LON)**

* [Amsterdam to London latency and RTT](/docs/network/latency/pairs/ams-lon-rtt) — 5.2 ms
* [Paris to London latency and RTT](/docs/network/latency/pairs/par-lon-rtt) — 6.4 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Marseille to London latency and RTT](/docs/network/latency/pairs/mrs-lon-rtt) — 18.9 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-lon.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Singapore → London 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-lon-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.
