Frankfurt
Backbone latency
- Average outbound
- 114.3ms
- Connected PoPs
- 19/ 19
Across 19 routes
19 inbound routes
Routes
Published ICMP round-trip measurements between Frankfurt and the other backbone PoPs. These are inter-PoP measurements, not last-mile speed tests.
| Details | |||
|---|---|---|---|
| AmsterdamAMS / Netherlands | 5.9 | 5.9 | |
| BerlinBER / Germany | 6.1 | 6.1 | |
| ParisPAR / France | 7.6 | 7.6 | |
| LondonLON / UK | 13.8 | 13.2 | |
| MarseilleMRS / France | 17.1 | 17.4 | |
| MoscowMOW / Russia | 36.2 | 36.3 | |
| New YorkNYC / USA | 73.9 | 74.4 | |
| AshburnIAD / USA | 81.1 | 80.9 | |
| MiamiMIA / USA | 112.2 | 112.5 | |
| SeattleSEA / USA | 133.7 | 135.3 | |
| Los AngelesLAX / USA | 137.8 | 140.0 | |
| Hong KongHKG / Hong Kong | 152.2 | 151.2 | |
| SingaporeSIN / Singapore | 152.9 | 152.0 | |
| TaipeiTPE / Taiwan | 166.4 | 165.3 | |
| São PauloGRU / Brazil | 181.6 | 186.5 | |
| JohannesburgJNB / South Africa | 189.1 | 166.0 | |
| TokyoTYO / Japan | 197.3 | 196.6 | |
| MelbourneMEL / Australia | 251.8 | 251.0 | |
| SydneySYD / Australia | 255.3 | 255.2 | |
RTT in ms. Outbound: probes from Frankfurt. Inbound: probes to Frankfurt.
Node & interconnection
- Network
- Hats Network / AS203314
- Location
- Frankfurt, Germany
- Facility
- FRA1
- Transit
- Not listed
- Peering / IX
- Not listed
- Region
- Europe

Frankfurt, Germany
City reference image
City reference: GeoNames 2925533; 50.11552, 8.68417. Coordinates refer to the city, not the facility.
Measurement notes
Why are outbound and inbound values different?
Outbound probes start at Frankfurt; 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.
Berlin network latency (BER)
Round-trip measurements between Berlin (BER) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.
London network latency (LON)
Round-trip measurements between London (LON) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.