Amsterdam
Backbone latency
- Average outbound
- 113.0ms
- Connected PoPs
- 19/ 19
Across 19 routes
19 inbound routes
Routes
Published ICMP round-trip measurements between Amsterdam and the other backbone PoPs. These are inter-PoP measurements, not last-mile speed tests.
| Details | |||
|---|---|---|---|
| LondonLON / UK | 5.1 | 5.1 | |
| FrankfurtFRA / Germany | 5.9 | 5.9 | |
| ParisPAR / France | 7.0 | 7.0 | |
| BerlinBER / Germany | 7.2 | 7.2 | |
| MarseilleMRS / France | 19.3 | 19.2 | |
| MoscowMOW / Russia | 40.1 | 39.5 | |
| New YorkNYC / USA | 69.0 | 68.2 | |
| AshburnIAD / USA | 76.1 | 75.4 | |
| MiamiMIA / USA | 108.8 | 107.6 | |
| SeattleSEA / USA | 130.1 | 130.3 | |
| Los AngelesLAX / USA | 134.5 | 133.6 | |
| Hong KongHKG / Hong Kong | 154.6 | 156.0 | |
| SingaporeSIN / Singapore | 157.1 | 156.3 | |
| TaipeiTPE / Taiwan | 170.6 | 168.9 | |
| JohannesburgJNB / South Africa | 171.9 | 163.1 | |
| São PauloGRU / Brazil | 176.7 | 181.6 | |
| TokyoTYO / Japan | 198.7 | 200.6 | |
| MelbourneMEL / Australia | 256.8 | 255.7 | |
| SydneySYD / Australia | 258.4 | 258.4 | |
RTT in ms. Outbound: probes from Amsterdam. Inbound: probes to Amsterdam.
Node & interconnection
- Network
- Hats Network / AS203314
- Location
- Amsterdam, Netherlands
- Facility
- AMS1
- Transit
- HE / Cogent / Telia / Liberty Global
- Peering / IX
- NL-IX @ ANS
- Region
- Europe
Amsterdam, Netherlands
City reference image
City reference: GeoNames 2759794; 52.37403, 4.88969. Coordinates refer to the city, not the facility.
Measurement notes
Why are outbound and inbound values different?
Outbound probes start at Amsterdam; inbound probes start at the remote PoP. Each value is a complete round trip. Routing, congestion and the measurement origin can produce different results in the two directions.
What do the probe statistics describe?
Minimum, maximum and standard deviation describe the published samples in each route's probe round. Each route includes its sample count, interval and timestamp. A short round does not establish long-term reliability or an SLA.
What is measured, and what is modeled?
The comparison table shows measured RTT. Fiber floors, efficiency, jitter estimates and trend comparisons on the individual route pages are calculated indicators. They do not identify a physical cable path or replace loss and jitter measurements. Read the methodology.
Measurement round: 2026-10-20T08:46:17Z. All PoPs / Dataset and licence.
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-10-20.
Berlin network latency (BER)
Round-trip measurements between Berlin (BER) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.