π©πͺ 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.
π©πͺ Berlin (BER)
Germany's capital and a growing digital hub, Berlin serves as the primary interconnection point between Eastern and Western European networks on the Hats Network backbone.
Measurement round: 2026-08-15T04:03:13Z.
This page provides round-trip time (RTT) latency metrics between the Berlin (BER) PoP and every other node on the Hats Network (AS203314) global backbone.

Average RTT from Berlin 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 Berlin (BER) 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) | 262.60 | 4.85 | 16,088 |
| Melbourne (MEL) | 255.80 | 10.50 | 15,965 |
| SΓ£o Paulo (GRU) | 188.00 | 8.06 | 10,232 |
| Tokyo (TYO) | 185.80 | 7.51 | 8,938 |
| Johannesburg (JNB) | 172.10 | 4.76 | 8,837 |
| Singapore (SIN) | 158.30 | 6.26 | 9,925 |
| Taipei (TPE) | 156.10 | 4.90 | 8,970 |
| Hong Kong (HKG) | 143.90 | 5.42 | 8,767 |
| Los Angeles (LAX) | 141.80 | 4.97 | 9,332 |
| Seattle (SEA) | 137.70 | 6.15 | 8,142 |
| Miami (MIA) | 117.80 | 5.45 | 8,010 |
| Ashburn (IAD) | 86.40 | 3.06 | 6,745 |
| New York (NYC) | 79.70 | 3.35 | 6,402 |
| Moscow (MOW) | 28.00 | 0.46 | 1,613 |
| Marseille (MRS) | 20.50 | 0.52 | 1,187 |
| London (LON) | 15.90 | 0.69 | 935 |
| Paris (PAR) | 14.20 | 0.59 | 881 |
| Amsterdam (AMS) | 7.20 | 0.24 | 579 |
| Frankfurt (FRA) | 6.10 | 0.11 | 425 |
RTT vs. distance from Berlin
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 Berlin. 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) | 262.60 | 16,088 |
| Melbourne (MEL) | 255.80 | 15,965 |
| SΓ£o Paulo (GRU) | 188.00 | 10,232 |
| Tokyo (TYO) | 185.80 | 8,938 |
| Johannesburg (JNB) | 172.10 | 8,837 |
| Singapore (SIN) | 158.30 | 9,925 |
| Taipei (TPE) | 156.10 | 8,970 |
| Hong Kong (HKG) | 143.90 | 8,767 |
| Los Angeles (LAX) | 141.80 | 9,332 |
| Seattle (SEA) | 137.70 | 8,142 |
| Miami (MIA) | 117.80 | 8,010 |
| Ashburn (IAD) | 86.40 | 6,745 |
| New York (NYC) | 79.70 | 6,402 |
| Moscow (MOW) | 28.00 | 1,613 |
| Marseille (MRS) | 20.50 | 1,187 |
| London (LON) | 15.90 | 935 |
| Paris (PAR) | 14.20 | 881 |
| Amsterdam (AMS) | 7.20 | 579 |
| Frankfurt (FRA) | 6.10 | 425 |
Fastest routes into Berlin
Measured RTT from 19 other PoPs into Berlin (BER), 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 Berlin (BER): 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 Berlin 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) |
|---|---|---|---|---|
| Frankfurt (FRA) | 6.10 | 5.88 | 6.72 | 425 |
| Amsterdam (AMS) | 7.20 | 6.92 | 7.88 | 579 |
| Paris (PAR) | 14.80 | 13.98 | 17.19 | 881 |
| London (LON) | 16.20 | 15.23 | 17.84 | 935 |
| Marseille (MRS) | 21.50 | 20.57 | 24.57 | 1,187 |
| Moscow (MOW) | 27.00 | 25.25 | 30.94 | 1,613 |
| New York (NYC) | 78.90 | 75.01 | 91.25 | 6,402 |
| Ashburn (IAD) | 86.70 | 84.12 | 93.74 | 6,745 |
| Miami (MIA) | 116.80 | 113.30 | 127.02 | 8,010 |
| Seattle (SEA) | 138.50 | 135.42 | 148.44 | 8,142 |
| Los Angeles (LAX) | 140.60 | 132.35 | 166.03 | 9,332 |
| Hong Kong (HKG) | 143.60 | 138.95 | 152.14 | 8,767 |
| Taipei (TPE) | 156.80 | 147.67 | 184.35 | 8,970 |
| Singapore (SIN) | 159.20 | 153.41 | 182.06 | 9,925 |
| Johannesburg (JNB) | 172.10 | 168.79 | 180.83 | 8,837 |
| Tokyo (TYO) | 186.40 | 177.43 | 207.75 | 8,938 |
| SΓ£o Paulo (GRU) | 190.80 | 181.19 | 208.39 | 10,232 |
| Melbourne (MEL) | 256.60 | 248.20 | 280.30 | 15,965 |
| Sydney (SYD) | 262.10 | 254.82 | 282.79 | 16,088 |
PoP Highlights
- Location: Berlin, Germany (Europe)
- Region: Europe
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 2950159 β 52.52437, 13.41053
- Coverage: RTT measurements to 19 other PoPs across 5 continents
Facility & Interconnection
- Facility: BER1
- Upstream transit: DE-CIX / RETN / NTT
- Peering / IX: BCIX
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | π©πͺ Berlin (BER) β π©πͺ Frankfurt (FRA) (6.1 ms) β Ultra-Low |
| Slowest Route | π©πͺ Berlin (BER) β π¦πΊ Sydney (SYD) (262.6 ms) |
| Average RTT | 114.6 ms |
| Average Jitter | 0.88 ms |
| Average Packet Loss | 0.06% |
| Best Fiber Efficiency | 78.8% |
| 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
Berlin sits on Hats Network's Europe backbone. Measured round-trip times to its 6 intra-region peers range from 6.1 ms (Frankfurt (FRA)) to 28 ms (Moscow (MOW)).
Berlin sits on the eastβwest European corridor, bridging the Western European hubs with Eastern European networks.
Outbound Latency from Berlin (BER)
Round-trip time in milliseconds from Berlin to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| π©πͺ Frankfurt (FRA) | 6.1 | 4.16 ms | 68.2% | 0.12 ms | 0.08% | Ultra-Low |
| π³π± Amsterdam (AMS) | 7.2 | 5.67 ms | 78.8% | 0.12 ms | 0.08% | Ultra-Low |
| π«π· Paris (PAR) | 14.2 | 8.62 ms | 60.7% | 0.12 ms | 0.12% | Ultra-Low |
| π¬π§ London (LON) | 15.9 | 9.15 ms | 57.6% | 0.12 ms | 0.12% | Ultra-Low |
| π«π· Marseille (MRS) | 20.5 | 11.62 ms | 56.7% | 0.15 ms | 0.04% | Ultra-Low |
| π·πΊ Moscow (MOW) | 28 | 15.8 ms | 56.4% | 0.22 ms | 0.07% | Ultra-Low |
| πΊπΈ New York (NYC) | 79.7 | 62.7 ms | 78.7% | 0.61 ms | 0.1% | Excellent |
| πΊπΈ Ashburn (IAD) | 86.4 | 66.05 ms | 76.4% | 0.61 ms | 0.15% | Good |
| πΊπΈ Miami (MIA) | 117.8 | 78.44 ms | 66.6% | 0.72 ms | 0.07% | Good |
| πΊπΈ Seattle (SEA) | 137.7 | 79.73 ms | 57.9% | 1.27 ms | 0.11% | Good |
| πΊπΈ Los Angeles (LAX) | 141.8 | 91.39 ms | 64.4% | 0.7 ms | 0% | Good |
| ππ° Hong Kong (HKG) | 143.9 | 85.85 ms | 59.7% | 1.6 ms | 0% | Good |
| πΉπΌ Taipei (TPE) | 156.1 | 87.84 ms | 56.3% | 0.83 ms | 0.01% | Fair |
| πΈπ¬ Singapore (SIN) | 158.3 | 97.19 ms | 61.4% | 0.96 ms | 0% | Fair |
| πΏπ¦ Johannesburg (JNB) | 172.1 | 86.53 ms | 50.3% | 1.15 ms | 0.09% | Fair |
| π―π΅ Tokyo (TYO) | 185.8 | 87.53 ms | 47.1% | 2.22 ms | 0% | Fair |
| π§π· SΓ£o Paulo (GRU) | 188 | 100.2 ms | 53.3% | 2.19 ms | 0% | Fair |
| π¦πΊ Melbourne (MEL) | 255.8 | 156.34 ms | 61.1% | 1.62 ms | 0% | High |
| π¦πΊ Sydney (SYD) | 262.6 | 157.54 ms | 60% | 1.34 ms | 0.07% | High |
Fastest Routes to Berlin (BER)
The 10 fastest measured routes to Berlin, 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 | π©πͺ Frankfurt (FRA) | 6.1 ms | 5.88 ms | 6.72 ms | 0.18 ms |
| 2 | π³π± Amsterdam (AMS) | 7.2 ms | 6.92 ms | 7.88 ms | 0.21 ms |
| 3 | π«π· Paris (PAR) | 14.8 ms | 13.98 ms | 17.19 ms | 0.68 ms |
| 4 | π¬π§ London (LON) | 16.2 ms | 15.23 ms | 17.84 ms | 0.56 ms |
| 5 | π«π· Marseille (MRS) | 21.5 ms | 20.57 ms | 24.57 ms | 0.92 ms |
| 6 | π·πΊ Moscow (MOW) | 27 ms | 25.25 ms | 30.94 ms | 1.32 ms |
| 7 | πΊπΈ New York (NYC) | 78.9 ms | 75.01 ms | 91.25 ms | 3.36 ms |
| 8 | πΊπΈ Ashburn (IAD) | 86.7 ms | 84.12 ms | 93.74 ms | 2.2 ms |
| 9 | πΊπΈ Miami (MIA) | 116.8 ms | 113.3 ms | 127.02 ms | 2.68 ms |
| 10 | πΊπΈ Seattle (SEA) | 138.5 ms | 135.42 ms | 148.44 ms | 3.11 ms |
Inbound Latency to Berlin (BER)
Round-trip time in milliseconds from all other PoPs to Berlin. 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 |
|---|---|---|---|---|---|---|
| π©πͺ Frankfurt (FRA) | 6.1 | 4.16 ms | 68.2% | 0.12 ms | 0.13% | Ultra-Low |
| π³π± Amsterdam (AMS) | 7.2 | 5.67 ms | 78.8% | 0.12 ms | 0.03% | Ultra-Low |
| π«π· Paris (PAR) | 14.8 | 8.62 ms | 58.3% | 0.13 ms | 0% | Ultra-Low |
| π¬π§ London (LON) | 16.2 | 9.15 ms | 56.5% | 0.15 ms | 0% | Ultra-Low |
| π«π· Marseille (MRS) | 21.5 | 11.62 ms | 54.1% | 0.18 ms | 0.16% | Ultra-Low |
| π·πΊ Moscow (MOW) | 27 | 15.8 ms | 58.5% | 0.26 ms | 0.11% | Ultra-Low |
| πΊπΈ New York (NYC) | 78.9 | 62.7 ms | 79.5% | 0.64 ms | 0% | Excellent |
| πΊπΈ Ashburn (IAD) | 86.7 | 66.05 ms | 76.2% | 0.77 ms | 0.15% | Good |
| πΊπΈ Miami (MIA) | 116.8 | 78.44 ms | 67.2% | 1.29 ms | 0.13% | Good |
| πΊπΈ Seattle (SEA) | 138.5 | 79.73 ms | 57.6% | 0.97 ms | 0% | Good |
| πΊπΈ Los Angeles (LAX) | 140.6 | 91.39 ms | 65% | 1.16 ms | 0% | Good |
| ππ° Hong Kong (HKG) | 143.6 | 85.85 ms | 59.8% | 1.27 ms | 0.11% | Good |
| πΉπΌ Taipei (TPE) | 156.8 | 87.84 ms | 56% | 1.81 ms | 0.18% | Fair |
| πΈπ¬ Singapore (SIN) | 159.2 | 97.19 ms | 61.1% | 1.11 ms | 0.06% | Fair |
| πΏπ¦ Johannesburg (JNB) | 172.1 | 86.53 ms | 50.3% | 1.1 ms | 0.06% | Fair |
| π―π΅ Tokyo (TYO) | 186.4 | 87.53 ms | 47% | 1.8 ms | 0.19% | Fair |
| π§π· SΓ£o Paulo (GRU) | 190.8 | 100.2 ms | 52.5% | 0.87 ms | 0.18% | Fair |
| π¦πΊ Melbourne (MEL) | 256.6 | 156.34 ms | 60.9% | 2.04 ms | 0.02% | High |
| π¦πΊ Sydney (SYD) | 262.1 | 157.54 ms | 60.1% | 1.83 ms | 0.19% | High |
Europe Peers
Berlin 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 | Netherlands | 7.2 | Ultra-Low |
| π©πͺ Frankfurt (FRA) | FRA | Germany | 6.1 | Ultra-Low |
| π¬π§ London (LON) | LON | UK | 15.9 | Ultra-Low |
| π«π· Marseille (MRS) | MRS | France | 20.5 | Ultra-Low |
| π·πΊ Moscow (MOW) | MOW | Russia | 28 | Ultra-Low |
| π«π· Paris (PAR) | PAR | France | 14.2 | Ultra-Low |
Frequently Asked Questions
What is the fastest route to Berlin?
The fastest measured route to Berlin (BER) is Frankfurt (FRA) β Berlin (BER), averaging 6.1 ms RTT (Ultra-Low).
What is the fastest route from Berlin?
The fastest measured route from Berlin (BER) is Berlin (BER) β Frankfurt (FRA), averaging 6.1 ms RTT (Ultra-Low).
How well connected is Berlin to the Hats Network backbone?
Berlin (BER) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, Berlin (BER) β Sydney (SYD), averages 262.6 ms RTT.
Open Data
Measured latency data for Berlin (BER) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:
- Per-route files β every directed route from Berlin is published as
ber-<destination>.pings.{csv,json,yaml}under/opendata/latency/latest/pairs/β for example ber-fra.pings.csv, the 50-probe ICMP echo round for Berlin (BER) β Frankfurt (FRA). - 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.
π³π± 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.
π©πͺ Frankfurt Ping & Network Latency (FRA) | AS203314
Frankfurt (FRA) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.