# 🇳🇱 Amsterdam Ping & Network Latency (AMS) | AS203314

## 🇳🇱 Amsterdam (AMS)

One of the world's most connected internet hubs — home to AMS-IX, the largest Internet Exchange globally. Hats Network peers directly with major European transit carriers at this PoP.

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

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

### PoP Highlights

* **Location:** Amsterdam, Netherlands (Europe)
* **Region:** Europe
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 2759794](https://www.geonames.org/2759794) — 52.37403, 4.88969
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** AMS1
* **Upstream transit:** HE / Cogent / Telia / Liberty Global
* **Peering / IX:** NL-IX @ ANS

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Fastest Route         | [🇳🇱 Amsterdam (AMS) → 🇬🇧 London (LON)](/docs/network/latency/pairs/ams-lon-rtt) (**5.2 ms**) — Ultra-Low |
| Slowest Route         | [🇳🇱 Amsterdam (AMS) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ams-syd-rtt) (**258 ms**)             |
| Average RTT           | **112.4 ms**                                                                                                 |
| Average Jitter        | **0.86 ms**                                                                                                  |
| Average Packet Loss   | **0.05%**                                                                                                    |
| Best Fiber Efficiency | **83.9%**                                                                                                    |
| 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

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

Amsterdam anchors the Northwest European corridor (London–Amsterdam–Frankfurt–Paris), one of the densest interconnection ecosystems in the world.

## Outbound Latency from Amsterdam (AMS)

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

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇬🇧 London (LON)       | **[5.2](/docs/network/latency/pairs/ams-lon-rtt)**   | 3.51 ms     | 67.4%      | 0.12 ms | 0.09% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[5.9](/docs/network/latency/pairs/ams-fra-rtt)**   | 3.57 ms     | 60.6%      | 0.12 ms | 0.05% | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[7](/docs/network/latency/pairs/ams-par-rtt)**     | 4.22 ms     | 60.3%      | 0.12 ms | 0.03% | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[7.2](/docs/network/latency/pairs/ams-ber-rtt)**   | 5.67 ms     | 78.8%      | 0.12 ms | 0.19% | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[19.6](/docs/network/latency/pairs/ams-mrs-rtt)**  | 9.89 ms     | 50.5%      | 0.12 ms | 0.03% | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[38.1](/docs/network/latency/pairs/ams-mow-rtt)**  | 21.1 ms     | 55.4%      | 0.38 ms | 0%    | Excellent |
| 🇺🇸 New York (NYC)     | **[68.6](/docs/network/latency/pairs/ams-nyc-rtt)**  | 57.56 ms    | 83.9%      | 0.31 ms | 0%    | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[75.7](/docs/network/latency/pairs/ams-iad-rtt)**  | 60.94 ms    | 80.5%      | 0.75 ms | 0.05% | Excellent |
| 🇺🇸 Miami (MIA)        | **[106](/docs/network/latency/pairs/ams-mia-rtt)**   | 73.03 ms    | 68.9%      | 1.03 ms | 0.01% | Good      |
| 🇺🇸 Seattle (SEA)      | **[130.2](/docs/network/latency/pairs/ams-sea-rtt)** | 76.86 ms    | 59%        | 1.26 ms | 0.04% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[133.7](/docs/network/latency/pairs/ams-lax-rtt)** | 87.74 ms    | 65.6%      | 0.65 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[155.9](/docs/network/latency/pairs/ams-hkg-rtt)** | 91.05 ms    | 58.4%      | 1.21 ms | 0.05% | Fair      |
| 🇸🇬 Singapore (SIN)    | **[157.6](/docs/network/latency/pairs/ams-sin-rtt)** | 102.86 ms   | 65.3%      | 0.82 ms | 0%    | Fair      |
| 🇹🇼 Taipei (TPE)       | **[168.7](/docs/network/latency/pairs/ams-tpe-rtt)** | 92.72 ms    | 55%        | 1.29 ms | 0.11% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[171.9](/docs/network/latency/pairs/ams-jnb-rtt)** | 88.05 ms    | 51.2%      | 1.1 ms  | 0.1%  | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[175.5](/docs/network/latency/pairs/ams-gru-rtt)** | 95.79 ms    | 54.6%      | 1.53 ms | 0%    | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[198.2](/docs/network/latency/pairs/ams-tyo-rtt)** | 91.18 ms    | 46%        | 1.27 ms | 0.14% | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[252.5](/docs/network/latency/pairs/ams-mel-rtt)** | 161.98 ms   | 64.1%      | 1.77 ms | 0.03% | High      |
| 🇦🇺 Sydney (SYD)       | **[258](/docs/network/latency/pairs/ams-syd-rtt)**   | 162.93 ms   | 63.2%      | 2.35 ms | 0.11% | High      |

## Fastest Routes to Amsterdam (AMS)

The 10 fastest measured routes **to Amsterdam**, 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    | 🇬🇧 London (LON)    | **[5.2 ms](/docs/network/latency/pairs/lon-ams-rtt)**   | 5.03 ms   | 5.75 ms   | 0.16 ms |
| 2    | 🇩🇪 Frankfurt (FRA) | **[5.9 ms](/docs/network/latency/pairs/fra-ams-rtt)**   | 5.62 ms   | 6.84 ms   | 0.25 ms |
| 3    | 🇫🇷 Paris (PAR)     | **[7 ms](/docs/network/latency/pairs/par-ams-rtt)**     | 6.65 ms   | 8.5 ms    | 0.33 ms |
| 4    | 🇩🇪 Berlin (BER)    | **[7.2 ms](/docs/network/latency/pairs/ber-ams-rtt)**   | 6.91 ms   | 7.91 ms   | 0.23 ms |
| 5    | 🇫🇷 Marseille (MRS) | **[20.3 ms](/docs/network/latency/pairs/mrs-ams-rtt)**  | 19.62 ms  | 22.75 ms  | 0.64 ms |
| 6    | 🇷🇺 Moscow (MOW)    | **[37.6 ms](/docs/network/latency/pairs/mow-ams-rtt)**  | 37.09 ms  | 39.9 ms   | 0.57 ms |
| 7    | 🇺🇸 New York (NYC)  | **[68.7 ms](/docs/network/latency/pairs/nyc-ams-rtt)**  | 66.97 ms  | 74.13 ms  | 1.38 ms |
| 8    | 🇺🇸 Ashburn (IAD)   | **[75.2 ms](/docs/network/latency/pairs/iad-ams-rtt)**  | 72.76 ms  | 84.12 ms  | 2.32 ms |
| 9    | 🇺🇸 Miami (MIA)     | **[106 ms](/docs/network/latency/pairs/mia-ams-rtt)**   | 103.48 ms | 113.5 ms  | 2.2 ms  |
| 10   | 🇺🇸 Seattle (SEA)   | **[128.6 ms](/docs/network/latency/pairs/sea-ams-rtt)** | 126.47 ms | 138.71 ms | 2.06 ms |

## Inbound Latency to Amsterdam (AMS)

Round-trip time in milliseconds **from all other PoPs to Amsterdam**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇬🇧 London (LON)       | **[5.2](/docs/network/latency/pairs/lon-ams-rtt)**   | 3.51 ms     | 67.4%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[5.9](/docs/network/latency/pairs/fra-ams-rtt)**   | 3.57 ms     | 60.6%      | 0.12 ms | 0%    | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[7](/docs/network/latency/pairs/par-ams-rtt)**     | 4.22 ms     | 60.3%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[7.2](/docs/network/latency/pairs/ber-ams-rtt)**   | 5.67 ms     | 78.8%      | 0.12 ms | 0%    | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[20.3](/docs/network/latency/pairs/mrs-ams-rtt)**  | 9.89 ms     | 48.7%      | 0.17 ms | 0.16% | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[37.6](/docs/network/latency/pairs/mow-ams-rtt)**  | 21.1 ms     | 56.1%      | 0.28 ms | 0.17% | Excellent |
| 🇺🇸 New York (NYC)     | **[68.7](/docs/network/latency/pairs/nyc-ams-rtt)**  | 57.56 ms    | 83.8%      | 0.33 ms | 0.03% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[75.2](/docs/network/latency/pairs/iad-ams-rtt)**  | 60.94 ms    | 81%        | 0.34 ms | 0.02% | Excellent |
| 🇺🇸 Miami (MIA)        | **[106](/docs/network/latency/pairs/mia-ams-rtt)**   | 73.03 ms    | 68.9%      | 0.87 ms | 0.08% | Good      |
| 🇺🇸 Seattle (SEA)      | **[128.6](/docs/network/latency/pairs/sea-ams-rtt)** | 76.86 ms    | 59.8%      | 1.46 ms | 0.13% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[132.1](/docs/network/latency/pairs/lax-ams-rtt)** | 87.74 ms    | 66.4%      | 0.78 ms | 0%    | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[154.4](/docs/network/latency/pairs/hkg-ams-rtt)** | 91.05 ms    | 59%        | 0.87 ms | 0%    | Fair      |
| 🇸🇬 Singapore (SIN)    | **[155.8](/docs/network/latency/pairs/sin-ams-rtt)** | 102.86 ms   | 66%        | 1.04 ms | 0.19% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[163.2](/docs/network/latency/pairs/jnb-ams-rtt)** | 88.05 ms    | 54%        | 1.84 ms | 0%    | Fair      |
| 🇹🇼 Taipei (TPE)       | **[166.5](/docs/network/latency/pairs/tpe-ams-rtt)** | 92.72 ms    | 55.7%      | 0.78 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[180](/docs/network/latency/pairs/gru-ams-rtt)**   | 95.79 ms    | 53.2%      | 1.53 ms | 0%    | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[197.4](/docs/network/latency/pairs/tyo-ams-rtt)** | 91.18 ms    | 46.2%      | 1.09 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[252.8](/docs/network/latency/pairs/mel-ams-rtt)** | 161.98 ms   | 64.1%      | 1.86 ms | 0%    | High      |
| 🇦🇺 Sydney (SYD)       | **[258.9](/docs/network/latency/pairs/syd-ams-rtt)** | 162.93 ms   | 62.9%      | 1.18 ms | 0.16% | High      |

## Europe Peers

Amsterdam 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      |
| --------------------------------------- | ---- | ------- | -------- | --------- |
| [🇩🇪 Berlin (BER)](./ber-berlin)       | BER  | Germany | **7.2**  | Ultra-Low |
| [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA  | Germany | **5.9**  | Ultra-Low |
| [🇬🇧 London (LON)](./lon-london)       | LON  | UK      | **5.2**  | Ultra-Low |
| [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS  | France  | **19.6** | Ultra-Low |
| [🇷🇺 Moscow (MOW)](./mow-moscow)       | MOW  | Russia  | **38.1** | Excellent |
| [🇫🇷 Paris (PAR)](./par-paris)         | PAR  | France  | **7**    | Ultra-Low |

## Frequently Asked Questions

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

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

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

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

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

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

## Open Data

Measured latency data for Amsterdam (AMS) 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 Amsterdam is published as `ams-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [ams-lon.pings.csv](/opendata/latency/latest/pairs/ams-lon.pings.csv), the 50-probe ICMP echo round for [Amsterdam (AMS) → London (LON)](/docs/network/latency/pairs/ams-lon-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/ams-amsterdam).
- **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.