🇳🇱 Amsterdam Ping & Network Latency (AMS) | AS203314
Amsterdam (AMS) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇳🇱 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-15T04:03:13Z.
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.
Average RTT from Amsterdam to every other PoP
Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round
How to read this chart
Each bar is the average round-trip time of one 50-probe ICMP echo round from Amsterdam (AMS) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.
Full 19-destination dataset
| Destination | Avg RTT (ms) | Stdev (ms) | Distance (km) |
|---|---|---|---|
| Sydney (SYD) | 260.90 | 12.86 | 16,638 |
| Melbourne (MEL) | 254.20 | 9.34 | 16,541 |
| Tokyo (TYO) | 198.00 | 8.45 | 9,311 |
| São Paulo (GRU) | 176.50 | 8.59 | 9,782 |
| Johannesburg (JNB) | 171.90 | 7.79 | 8,992 |
| Taipei (TPE) | 167.20 | 4.26 | 9,468 |
| Singapore (SIN) | 158.20 | 7.26 | 10,503 |
| Hong Kong (HKG) | 152.80 | 6.24 | 9,298 |
| Los Angeles (LAX) | 134.60 | 3.97 | 8,960 |
| Seattle (SEA) | 130.10 | 1.97 | 7,849 |
| Miami (MIA) | 107.80 | 4.13 | 7,458 |
| Ashburn (IAD) | 75.70 | 3.20 | 6,223 |
| New York (NYC) | 68.20 | 1.21 | 5,878 |
| Moscow (MOW) | 38.20 | 1.46 | 2,155 |
| Marseille (MRS) | 19.70 | 0.81 | 1,010 |
| Berlin (BER) | 7.20 | 0.21 | 579 |
| Paris (PAR) | 7.00 | 0.17 | 431 |
| Frankfurt (FRA) | 5.90 | 0.26 | 365 |
| London (LON) | 5.10 | 0.12 | 358 |
RTT vs. distance from Amsterdam
Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent
How to read this chart
Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from Amsterdam. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).
Underlying measurements
| Destination | Avg RTT (ms) | Distance (km) |
|---|---|---|
| Sydney (SYD) | 260.90 | 16,638 |
| Melbourne (MEL) | 254.20 | 16,541 |
| Tokyo (TYO) | 198.00 | 9,311 |
| São Paulo (GRU) | 176.50 | 9,782 |
| Johannesburg (JNB) | 171.90 | 8,992 |
| Taipei (TPE) | 167.20 | 9,468 |
| Singapore (SIN) | 158.20 | 10,503 |
| Hong Kong (HKG) | 152.80 | 9,298 |
| Los Angeles (LAX) | 134.60 | 8,960 |
| Seattle (SEA) | 130.10 | 7,849 |
| Miami (MIA) | 107.80 | 7,458 |
| Ashburn (IAD) | 75.70 | 6,223 |
| New York (NYC) | 68.20 | 5,878 |
| Moscow (MOW) | 38.20 | 2,155 |
| Marseille (MRS) | 19.70 | 1,010 |
| Berlin (BER) | 7.20 | 579 |
| Paris (PAR) | 7.00 | 431 |
| Frankfurt (FRA) | 5.90 | 365 |
| London (LON) | 5.10 | 358 |
Fastest routes into Amsterdam
Measured RTT from 19 other PoPs into Amsterdam (AMS), sorted fastest first · each row spans min–max with a dot at the average
How to read this chart
Each row is one 50-probe ICMP echo round from another PoP into Amsterdam (AMS): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into Amsterdam can differ from the outbound path shown in the charts above.
Full 19-source dataset
| Source | Avg RTT (ms) | Min (ms) | Max (ms) | Distance (km) |
|---|---|---|---|---|
| London (LON) | 5.10 | 4.80 | 5.88 | 358 |
| Frankfurt (FRA) | 5.90 | 5.53 | 6.92 | 365 |
| Paris (PAR) | 7.00 | 6.78 | 7.81 | 431 |
| Berlin (BER) | 7.20 | 6.98 | 8.07 | 579 |
| Marseille (MRS) | 19.60 | 19.21 | 20.60 | 1,010 |
| Moscow (MOW) | 39.30 | 37.75 | 43.59 | 2,155 |
| New York (NYC) | 68.50 | 67.12 | 72.46 | 5,878 |
| Ashburn (IAD) | 75.70 | 73.24 | 82.29 | 6,223 |
| Miami (MIA) | 107.30 | 101.52 | 121.91 | 7,458 |
| Seattle (SEA) | 129.60 | 124.65 | 139.62 | 7,849 |
| Los Angeles (LAX) | 133.40 | 129.72 | 148.28 | 8,960 |
| Hong Kong (HKG) | 154.30 | 151.37 | 165.22 | 9,298 |
| Singapore (SIN) | 157.30 | 149.78 | 176.63 | 10,503 |
| Johannesburg (JNB) | 163.10 | 158.94 | 176.45 | 8,992 |
| Taipei (TPE) | 167.40 | 157.78 | 189.63 | 9,468 |
| São Paulo (GRU) | 181.30 | 173.45 | 206.55 | 9,782 |
| Tokyo (TYO) | 197.40 | 191.06 | 217.26 | 9,311 |
| Melbourne (MEL) | 252.50 | 243.54 | 283.04 | 16,541 |
| Sydney (SYD) | 259.20 | 252.22 | 273.10 | 16,638 |
PoP Highlights
- Location: Amsterdam, Netherlands (Europe)
- Region: Europe
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 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
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇳🇱 Amsterdam (AMS) → 🇬🇧 London (LON) (5.1 ms) — Ultra-Low |
| Slowest Route | 🇳🇱 Amsterdam (AMS) → 🇦🇺 Sydney (SYD) (260.9 ms) |
| Average RTT | 112.6 ms |
| Average Jitter | 0.94 ms |
| Average Packet Loss | 0.08% |
| Best Fiber Efficiency | 84.4% |
| 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.
Geographic & Network Position
Amsterdam sits on Hats Network's Europe backbone. Measured round-trip times to its 6 intra-region peers range from 5.1 ms (London (LON)) to 38.2 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.1 | 3.51 ms | 68.7% | 0.12 ms | 0% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | 5.9 | 3.57 ms | 60.6% | 0.12 ms | 0% | Ultra-Low |
| 🇫🇷 Paris (PAR) | 7 | 4.22 ms | 60.3% | 0.12 ms | 0% | Ultra-Low |
| 🇩🇪 Berlin (BER) | 7.2 | 5.67 ms | 78.8% | 0.12 ms | 0.03% | Ultra-Low |
| 🇫🇷 Marseille (MRS) | 19.7 | 9.89 ms | 50.2% | 0.22 ms | 0% | Ultra-Low |
| 🇷🇺 Moscow (MOW) | 38.2 | 21.1 ms | 55.2% | 0.26 ms | 0% | Excellent |
| 🇺🇸 New York (NYC) | 68.2 | 57.56 ms | 84.4% | 0.37 ms | 0.12% | Excellent |
| 🇺🇸 Ashburn (IAD) | 75.7 | 60.94 ms | 80.5% | 0.88 ms | 0.07% | Excellent |
| 🇺🇸 Miami (MIA) | 107.8 | 73.03 ms | 67.7% | 0.55 ms | 0.09% | Good |
| 🇺🇸 Seattle (SEA) | 130.1 | 76.86 ms | 59.1% | 1.14 ms | 0.11% | Good |
| 🇺🇸 Los Angeles (LAX) | 134.6 | 87.74 ms | 65.2% | 1.28 ms | 0% | Good |
| 🇭🇰 Hong Kong (HKG) | 152.8 | 91.05 ms | 59.6% | 1.18 ms | 0.02% | Fair |
| 🇸🇬 Singapore (SIN) | 158.2 | 102.86 ms | 65% | 1.67 ms | 0.07% | Fair |
| 🇹🇼 Taipei (TPE) | 167.2 | 92.72 ms | 55.5% | 1.45 ms | 0.19% | Fair |
| 🇿🇦 Johannesburg (JNB) | 171.9 | 88.05 ms | 51.2% | 1.4 ms | 0.15% | Fair |
| 🇧🇷 São Paulo (GRU) | 176.5 | 95.79 ms | 54.3% | 1.62 ms | 0.17% | Fair |
| 🇯🇵 Tokyo (TYO) | 198 | 91.18 ms | 46.1% | 2 ms | 0.18% | Fair |
| 🇦🇺 Melbourne (MEL) | 254.2 | 161.98 ms | 63.7% | 1.73 ms | 0.16% | High |
| 🇦🇺 Sydney (SYD) | 260.9 | 162.93 ms | 62.5% | 1.63 ms | 0.18% | 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.1 ms | 4.8 ms | 5.88 ms | 0.24 ms |
| 2 | 🇩🇪 Frankfurt (FRA) | 5.9 ms | 5.53 ms | 6.92 ms | 0.29 ms |
| 3 | 🇫🇷 Paris (PAR) | 7 ms | 6.78 ms | 7.81 ms | 0.23 ms |
| 4 | 🇩🇪 Berlin (BER) | 7.2 ms | 6.98 ms | 8.07 ms | 0.24 ms |
| 5 | 🇫🇷 Marseille (MRS) | 19.6 ms | 19.21 ms | 20.6 ms | 0.3 ms |
| 6 | 🇷🇺 Moscow (MOW) | 39.3 ms | 37.75 ms | 43.59 ms | 1.46 ms |
| 7 | 🇺🇸 New York (NYC) | 68.5 ms | 67.12 ms | 72.46 ms | 1.18 ms |
| 8 | 🇺🇸 Ashburn (IAD) | 75.7 ms | 73.24 ms | 82.29 ms | 1.9 ms |
| 9 | 🇺🇸 Miami (MIA) | 107.3 ms | 101.52 ms | 121.91 ms | 4.57 ms |
| 10 | 🇺🇸 Seattle (SEA) | 129.6 ms | 124.65 ms | 139.62 ms | 3.82 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.1 | 3.51 ms | 68.7% | 0.12 ms | 0% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | 5.9 | 3.57 ms | 60.6% | 0.12 ms | 0.09% | Ultra-Low |
| 🇫🇷 Paris (PAR) | 7 | 4.22 ms | 60.3% | 0.12 ms | 0.18% | Ultra-Low |
| 🇩🇪 Berlin (BER) | 7.2 | 5.67 ms | 78.8% | 0.12 ms | 0.08% | Ultra-Low |
| 🇫🇷 Marseille (MRS) | 19.6 | 9.89 ms | 50.5% | 0.13 ms | 0.2% | Ultra-Low |
| 🇷🇺 Moscow (MOW) | 39.3 | 21.1 ms | 53.7% | 0.28 ms | 0% | Excellent |
| 🇺🇸 New York (NYC) | 68.5 | 57.56 ms | 84% | 0.55 ms | 0.17% | Excellent |
| 🇺🇸 Ashburn (IAD) | 75.7 | 60.94 ms | 80.5% | 0.69 ms | 0% | Excellent |
| 🇺🇸 Miami (MIA) | 107.3 | 73.03 ms | 68.1% | 0.91 ms | 0.12% | Good |
| 🇺🇸 Seattle (SEA) | 129.6 | 76.86 ms | 59.3% | 1.02 ms | 0% | Good |
| 🇺🇸 Los Angeles (LAX) | 133.4 | 87.74 ms | 65.8% | 1.11 ms | 0% | Good |
| 🇭🇰 Hong Kong (HKG) | 154.3 | 91.05 ms | 59% | 1.11 ms | 0.04% | Fair |
| 🇸🇬 Singapore (SIN) | 157.3 | 102.86 ms | 65.4% | 1.21 ms | 0.06% | Fair |
| 🇿🇦 Johannesburg (JNB) | 163.1 | 88.05 ms | 54% | 1.09 ms | 0.11% | Fair |
| 🇹🇼 Taipei (TPE) | 167.4 | 92.72 ms | 55.4% | 1.97 ms | 0% | Fair |
| 🇧🇷 São Paulo (GRU) | 181.3 | 95.79 ms | 52.8% | 1.82 ms | 0% | Fair |
| 🇯🇵 Tokyo (TYO) | 197.4 | 91.18 ms | 46.2% | 1.76 ms | 0.05% | Fair |
| 🇦🇺 Melbourne (MEL) | 252.5 | 161.98 ms | 64.1% | 2.36 ms | 0.14% | High |
| 🇦🇺 Sydney (SYD) | 259.2 | 162.93 ms | 62.9% | 2.52 ms | 0% | 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 | Germany | 7.2 | Ultra-Low |
| 🇩🇪 Frankfurt (FRA) | FRA | Germany | 5.9 | Ultra-Low |
| 🇬🇧 London (LON) | LON | UK | 5.1 | Ultra-Low |
| 🇫🇷 Marseille (MRS) | MRS | France | 19.7 | Ultra-Low |
| 🇷🇺 Moscow (MOW) | MOW | Russia | 38.2 | Excellent |
| 🇫🇷 Paris (PAR) | 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), averaging 5.1 ms RTT (Ultra-Low).
What is the fastest route from Amsterdam?
The fastest measured route from Amsterdam (AMS) is Amsterdam (AMS) → London (LON), averaging 5.1 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), averages 260.9 ms RTT.
Open Data
Measured latency data for Amsterdam (AMS) is published daily under CC 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/— for example ams-lon.pings.csv, the 50-probe ICMP echo round for Amsterdam (AMS) → London (LON). - Dataset documentation — /opendata/latency/ covers file formats, versioning, checksums, and the aggregated full-matrix releases.
Data auto-generated on August 15, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.
City-to-City Ping & RTT Latency | AS203314
Compare city-to-city ping, RTT, jitter, loss, theoretical fiber limits, and route efficiency across Hats Network (AS203314) PoPs. Updated 2026-08-15.
🇩🇪 Berlin Ping & Network Latency (BER) | AS203314
Berlin (BER) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.