# 🇬🇧 London Ping & Network Latency (LON) | AS203314

## 🇬🇧 London (LON)

London is Europe's transatlantic gateway, connecting European networks to North America. Hats Network's London PoP provides low-latency paths to both continents.

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

This page provides round-trip time (RTT) latency metrics between the **London (LON)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** London, UK (Europe)
* **Region:** Europe
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 2643743](https://www.geonames.org/2643743) — 51.50853, -0.12574
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** LON1
* **Upstream transit:** HE / Cogent / LINX
* **Peering / IX:** LINX / DE-CIX London

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Fastest Route         | [🇬🇧 London (LON) → 🇳🇱 Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt) (**5.2 ms**) — Ultra-Low |
| Slowest Route         | [🇬🇧 London (LON) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/lon-syd-rtt) (**258.1 ms**)              |
| Average RTT           | **112.7 ms**                                                                                                 |
| Average Jitter        | **0.83 ms**                                                                                                  |
| Average Packet Loss   | **0.06%**                                                                                                    |
| Best Fiber Efficiency | **85.7%**                                                                                                    |
| Intra-Region Peers    | 6 PoPs in Europe                                                                                             |
| Total Routes          | 19 outbound / 19 inbound (100% coverage)                                                                     |

> Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the [theoretical fiber latency methodology](/docs/network/latency/theoretical-fiber-latency).

## Geographic & Network Position

London sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **5.2 ms** (Amsterdam (AMS)) to **43.5 ms** (Moscow (MOW)).

London is the western anchor of the Northwest European corridor and Europe's traditional transatlantic gateway.

## Outbound Latency from London (LON)

Round-trip time in milliseconds **from London** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇳🇱 Amsterdam (AMS)    | **[5.2](/docs/network/latency/pairs/lon-ams-rtt)**   | 3.51 ms     | 67.4%      | 0.12 ms | 0%    | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[6.4](/docs/network/latency/pairs/lon-par-rtt)**   | 3.37 ms     | 52.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[13.6](/docs/network/latency/pairs/lon-fra-rtt)**  | 6.26 ms     | 46.1%      | 0.12 ms | 0.03% | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[16.2](/docs/network/latency/pairs/lon-ber-rtt)**  | 9.15 ms     | 56.5%      | 0.12 ms | 0.02% | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[17.9](/docs/network/latency/pairs/lon-mrs-rtt)**  | 9.82 ms     | 54.8%      | 0.16 ms | 0.14% | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[43.5](/docs/network/latency/pairs/lon-mow-rtt)**  | 24.56 ms    | 56.5%      | 0.2 ms  | 0.06% | Excellent |
| 🇺🇸 New York (NYC)     | **[63.8](/docs/network/latency/pairs/lon-nyc-rtt)**  | 54.69 ms    | 85.7%      | 0.42 ms | 0.12% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[71](/docs/network/latency/pairs/lon-iad-rtt)**    | 58.1 ms     | 81.8%      | 0.52 ms | 0.13% | Excellent |
| 🇺🇸 Miami (MIA)        | **[101.9](/docs/network/latency/pairs/lon-mia-rtt)** | 69.9 ms     | 68.6%      | 0.83 ms | 0.1%  | Good      |
| 🇺🇸 Seattle (SEA)      | **[123.2](/docs/network/latency/pairs/lon-sea-rtt)** | 75.63 ms    | 61.4%      | 0.95 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[127.5](/docs/network/latency/pairs/lon-lax-rtt)** | 85.95 ms    | 67.4%      | 0.86 ms | 0.17% | Good      |
| 🇸🇬 Singapore (SIN)    | **[156.5](/docs/network/latency/pairs/lon-sin-rtt)** | 106.35 ms   | 68%        | 1.57 ms | 0%    | Fair      |
| 🇭🇰 Hong Kong (HKG)    | **[160.6](/docs/network/latency/pairs/lon-hkg-rtt)** | 94.44 ms    | 58.8%      | 0.84 ms | 0.07% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[170.7](/docs/network/latency/pairs/lon-gru-rtt)** | 92.76 ms    | 54.3%      | 1.06 ms | 0.02% | Fair      |
| 🇹🇼 Taipei (TPE)       | **[173.8](/docs/network/latency/pairs/lon-tpe-rtt)** | 95.97 ms    | 55.2%      | 1.58 ms | 0.09% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[179.6](/docs/network/latency/pairs/lon-jnb-rtt)** | 88.52 ms    | 49.3%      | 0.86 ms | 0%    | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[202.9](/docs/network/latency/pairs/lon-tyo-rtt)** | 93.84 ms    | 46.2%      | 1.61 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[249.6](/docs/network/latency/pairs/lon-mel-rtt)** | 165.48 ms   | 66.3%      | 2.17 ms | 0%    | Fair      |
| 🇦🇺 Sydney (SYD)       | **[258.1](/docs/network/latency/pairs/lon-syd-rtt)** | 166.37 ms   | 64.5%      | 1.58 ms | 0.18% | High      |

## Fastest Routes to London (LON)

The 10 fastest measured routes **to London**, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.

| Rank | Source               | Avg RTT                                                 | Min       | Max       | Stdev   |
| ---- | -------------------- | ------------------------------------------------------- | --------- | --------- | ------- |
| 1    | 🇳🇱 Amsterdam (AMS) | **[5.2 ms](/docs/network/latency/pairs/ams-lon-rtt)**   | 4.89 ms   | 5.85 ms   | 0.25 ms |
| 2    | 🇫🇷 Paris (PAR)     | **[6.4 ms](/docs/network/latency/pairs/par-lon-rtt)**   | 6.03 ms   | 7.35 ms   | 0.26 ms |
| 3    | 🇩🇪 Frankfurt (FRA) | **[12.9 ms](/docs/network/latency/pairs/fra-lon-rtt)**  | 12.38 ms  | 14.46 ms  | 0.43 ms |
| 4    | 🇩🇪 Berlin (BER)    | **[15.2 ms](/docs/network/latency/pairs/ber-lon-rtt)**  | 14.57 ms  | 16.96 ms  | 0.49 ms |
| 5    | 🇫🇷 Marseille (MRS) | **[18.9 ms](/docs/network/latency/pairs/mrs-lon-rtt)**  | 18.41 ms  | 20.09 ms  | 0.42 ms |
| 6    | 🇷🇺 Moscow (MOW)    | **[42.4 ms](/docs/network/latency/pairs/mow-lon-rtt)**  | 40.38 ms  | 48.72 ms  | 1.83 ms |
| 7    | 🇺🇸 New York (NYC)  | **[63.5 ms](/docs/network/latency/pairs/nyc-lon-rtt)**  | 61.91 ms  | 68.19 ms  | 1.32 ms |
| 8    | 🇺🇸 Ashburn (IAD)   | **[70.3 ms](/docs/network/latency/pairs/iad-lon-rtt)**  | 68.79 ms  | 73.78 ms  | 1.22 ms |
| 9    | 🇺🇸 Miami (MIA)     | **[101.8 ms](/docs/network/latency/pairs/mia-lon-rtt)** | 96.22 ms  | 114.36 ms | 3.81 ms |
| 10   | 🇺🇸 Seattle (SEA)   | **[124.1 ms](/docs/network/latency/pairs/sea-lon-rtt)** | 118.94 ms | 137.2 ms  | 3.96 ms |

## Inbound Latency to London (LON)

Round-trip time in milliseconds **from all other PoPs to London**. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.

| Source                  | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇳🇱 Amsterdam (AMS)    | **[5.2](/docs/network/latency/pairs/ams-lon-rtt)**   | 3.51 ms     | 67.4%      | 0.12 ms | 0.09% | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[6.4](/docs/network/latency/pairs/par-lon-rtt)**   | 3.37 ms     | 52.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[12.9](/docs/network/latency/pairs/fra-lon-rtt)**  | 6.26 ms     | 48.5%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[15.2](/docs/network/latency/pairs/ber-lon-rtt)**  | 9.15 ms     | 60.2%      | 0.15 ms | 0.14% | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[18.9](/docs/network/latency/pairs/mrs-lon-rtt)**  | 9.82 ms     | 51.9%      | 0.15 ms | 0.09% | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[42.4](/docs/network/latency/pairs/mow-lon-rtt)**  | 24.56 ms    | 57.9%      | 0.46 ms | 0.18% | Excellent |
| 🇺🇸 New York (NYC)     | **[63.5](/docs/network/latency/pairs/nyc-lon-rtt)**  | 54.69 ms    | 86.1%      | 0.7 ms  | 0.01% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[70.3](/docs/network/latency/pairs/iad-lon-rtt)**  | 58.1 ms     | 82.6%      | 0.81 ms | 0.19% | Excellent |
| 🇺🇸 Miami (MIA)        | **[101.8](/docs/network/latency/pairs/mia-lon-rtt)** | 69.9 ms     | 68.7%      | 0.73 ms | 0%    | Good      |
| 🇺🇸 Seattle (SEA)      | **[124.1](/docs/network/latency/pairs/sea-lon-rtt)** | 75.63 ms    | 60.9%      | 1.38 ms | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[129.2](/docs/network/latency/pairs/lax-lon-rtt)** | 85.95 ms    | 66.5%      | 1.17 ms | 0%    | Good      |
| 🇸🇬 Singapore (SIN)    | **[155.4](/docs/network/latency/pairs/sin-lon-rtt)** | 106.35 ms   | 68.4%      | 1.17 ms | 0.06% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[158](/docs/network/latency/pairs/jnb-lon-rtt)**   | 88.52 ms    | 56%        | 0.77 ms | 0.12% | Fair      |
| 🇭🇰 Hong Kong (HKG)    | **[158.7](/docs/network/latency/pairs/hkg-lon-rtt)** | 94.44 ms    | 59.5%      | 0.8 ms  | 0%    | Fair      |
| 🇹🇼 Taipei (TPE)       | **[173](/docs/network/latency/pairs/tpe-lon-rtt)**   | 95.97 ms    | 55.5%      | 1.51 ms | 0.16% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[175.8](/docs/network/latency/pairs/gru-lon-rtt)** | 92.76 ms    | 52.8%      | 1.62 ms | 0%    | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[202.7](/docs/network/latency/pairs/tyo-lon-rtt)** | 93.84 ms    | 46.3%      | 0.93 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[252](/docs/network/latency/pairs/mel-lon-rtt)**   | 165.48 ms   | 65.7%      | 2.3 ms  | 0.04% | High      |
| 🇦🇺 Sydney (SYD)       | **[256.5](/docs/network/latency/pairs/syd-lon-rtt)** | 166.37 ms   | 64.9%      | 2.97 ms | 0.09% | High      |

## Europe Peers

London is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity.

| PoP                                     | Code | Country     | RTT (ms) | Tier      |
| --------------------------------------- | ---- | ----------- | -------- | --------- |
| [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS  | Netherlands | **5.2**  | Ultra-Low |
| [🇩🇪 Berlin (BER)](./ber-berlin)       | BER  | Germany     | **16.2** | Ultra-Low |
| [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA  | Germany     | **13.6** | Ultra-Low |
| [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS  | France      | **17.9** | Ultra-Low |
| [🇷🇺 Moscow (MOW)](./mow-moscow)       | MOW  | Russia      | **43.5** | Excellent |
| [🇫🇷 Paris (PAR)](./par-paris)         | PAR  | France      | **6.4**  | Ultra-Low |

## Frequently Asked Questions

**What is the fastest route to London?**

The fastest measured route to London (LON) is [Amsterdam (AMS) → London (LON)](/docs/network/latency/pairs/ams-lon-rtt), averaging **5.2 ms** RTT (Ultra-Low).

**What is the fastest route from London?**

The fastest measured route from London (LON) is [London (LON) → Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt), averaging **5.2 ms** RTT (Ultra-Low).

**How well connected is London to the Hats Network backbone?**

London (LON) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [London (LON) → Sydney (SYD)](/docs/network/latency/pairs/lon-syd-rtt), averages **258.1 ms** RTT.

## Open Data

Measured latency data for London (LON) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) as part of the Hats Network open latency dataset:

* **Per-route files** — every directed route from London is published as `lon-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [lon-ams.pings.csv](/opendata/latency/latest/pairs/lon-ams.pings.csv), the 50-probe ICMP echo round for [London (LON) → Amsterdam (AMS)](/docs/network/latency/pairs/lon-ams-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/lon-london).
- **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.