# 🇩🇪 Berlin Ping & Network Latency (BER) | AS203314

## 🇩🇪 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-16T04:07:28Z`.

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.

### PoP Highlights

* **Location:** Berlin, Germany (Europe)
* **Region:** Europe
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 2950159](https://www.geonames.org/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

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| Fastest Route         | [🇩🇪 Berlin (BER) → 🇩🇪 Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-rtt) (**6.1 ms**) — Ultra-Low |
| Slowest Route         | [🇩🇪 Berlin (BER) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/ber-syd-rtt) (**262.1 ms**)              |
| Average RTT           | **114.8 ms**                                                                                                 |
| Average Jitter        | **1.11 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](/docs/network/latency/theoretical-fiber-latency).

## 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.6 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](/docs/network/latency/pairs/ber-fra-rtt)**   | 4.16 ms     | 68.2%      | 0.12 ms | 0%    | Ultra-Low |
| 🇳🇱 Amsterdam (AMS)    | **[7.2](/docs/network/latency/pairs/ber-ams-rtt)**   | 5.67 ms     | 78.8%      | 0.12 ms | 0%    | Ultra-Low |
| 🇬🇧 London (LON)       | **[15.2](/docs/network/latency/pairs/ber-lon-rtt)**  | 9.15 ms     | 60.2%      | 0.15 ms | 0.14% | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[15.6](/docs/network/latency/pairs/ber-par-rtt)**  | 8.62 ms     | 55.3%      | 0.16 ms | 0%    | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[20.2](/docs/network/latency/pairs/ber-mrs-rtt)**  | 11.62 ms    | 57.5%      | 0.16 ms | 0.06% | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[28.6](/docs/network/latency/pairs/ber-mow-rtt)**  | 15.8 ms     | 55.2%      | 0.33 ms | 0%    | Ultra-Low |
| 🇺🇸 New York (NYC)     | **[79.6](/docs/network/latency/pairs/ber-nyc-rtt)**  | 62.7 ms     | 78.8%      | 0.5 ms  | 0.08% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[85.7](/docs/network/latency/pairs/ber-iad-rtt)**  | 66.05 ms    | 77.1%      | 0.79 ms | 0%    | Good      |
| 🇺🇸 Miami (MIA)        | **[118.3](/docs/network/latency/pairs/ber-mia-rtt)** | 78.44 ms    | 66.3%      | 0.76 ms | 0%    | Good      |
| 🇺🇸 Seattle (SEA)      | **[139.7](/docs/network/latency/pairs/ber-sea-rtt)** | 79.73 ms    | 57.1%      | 1.63 ms | 0.2%  | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[140.9](/docs/network/latency/pairs/ber-lax-rtt)** | 91.39 ms    | 64.9%      | 1.62 ms | 0.1%  | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[144.9](/docs/network/latency/pairs/ber-hkg-rtt)** | 85.85 ms    | 59.3%      | 1.29 ms | 0.08% | Good      |
| 🇹🇼 Taipei (TPE)       | **[156.8](/docs/network/latency/pairs/ber-tpe-rtt)** | 87.84 ms    | 56%        | 1.45 ms | 0.17% | Fair      |
| 🇸🇬 Singapore (SIN)    | **[158.3](/docs/network/latency/pairs/ber-sin-rtt)** | 97.19 ms    | 61.4%      | 0.87 ms | 0.19% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[172.1](/docs/network/latency/pairs/ber-jnb-rtt)** | 86.53 ms    | 50.3%      | 1.56 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[186.5](/docs/network/latency/pairs/ber-gru-rtt)** | 100.2 ms    | 53.7%      | 2.2 ms  | 0.01% | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[187.5](/docs/network/latency/pairs/ber-tyo-rtt)** | 87.53 ms    | 46.7%      | 1.21 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[256.2](/docs/network/latency/pairs/ber-mel-rtt)** | 156.34 ms   | 61%        | 3.01 ms | 0.03% | High      |
| 🇦🇺 Sydney (SYD)       | **[262.1](/docs/network/latency/pairs/ber-syd-rtt)** | 157.54 ms   | 60.1%      | 3.1 ms  | 0.15% | 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](/docs/network/latency/pairs/fra-ber-rtt)**   | 5.91 ms   | 6.79 ms   | 0.18 ms |
| 2    | 🇳🇱 Amsterdam (AMS)   | **[7.2 ms](/docs/network/latency/pairs/ams-ber-rtt)**   | 6.88 ms   | 8.21 ms   | 0.31 ms |
| 3    | 🇫🇷 Paris (PAR)       | **[15.5 ms](/docs/network/latency/pairs/par-ber-rtt)**  | 14.87 ms  | 17.28 ms  | 0.57 ms |
| 4    | 🇬🇧 London (LON)      | **[16.2 ms](/docs/network/latency/pairs/lon-ber-rtt)**  | 15.5 ms   | 19.35 ms  | 0.73 ms |
| 5    | 🇫🇷 Marseille (MRS)   | **[20.6 ms](/docs/network/latency/pairs/mrs-ber-rtt)**  | 19.99 ms  | 21.74 ms  | 0.35 ms |
| 6    | 🇷🇺 Moscow (MOW)      | **[27.5 ms](/docs/network/latency/pairs/mow-ber-rtt)**  | 26.72 ms  | 29.96 ms  | 0.74 ms |
| 7    | 🇺🇸 New York (NYC)    | **[78.8 ms](/docs/network/latency/pairs/nyc-ber-rtt)**  | 77.15 ms  | 84.9 ms   | 1.59 ms |
| 8    | 🇺🇸 Ashburn (IAD)     | **[86.1 ms](/docs/network/latency/pairs/iad-ber-rtt)**  | 84.07 ms  | 94.45 ms  | 2.05 ms |
| 9    | 🇺🇸 Miami (MIA)       | **[117.3 ms](/docs/network/latency/pairs/mia-ber-rtt)** | 113.83 ms | 127.02 ms | 2.73 ms |
| 10   | 🇺🇸 Los Angeles (LAX) | **[139.3 ms](/docs/network/latency/pairs/lax-ber-rtt)** | 136.33 ms | 148.84 ms | 2.96 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](/docs/network/latency/pairs/fra-ber-rtt)**   | 4.16 ms     | 68.2%      | 0.12 ms | 0%    | Ultra-Low |
| 🇳🇱 Amsterdam (AMS)    | **[7.2](/docs/network/latency/pairs/ams-ber-rtt)**   | 5.67 ms     | 78.8%      | 0.12 ms | 0.19% | Ultra-Low |
| 🇫🇷 Paris (PAR)        | **[15.5](/docs/network/latency/pairs/par-ber-rtt)**  | 8.62 ms     | 55.6%      | 0.13 ms | 0%    | Ultra-Low |
| 🇬🇧 London (LON)       | **[16.2](/docs/network/latency/pairs/lon-ber-rtt)**  | 9.15 ms     | 56.5%      | 0.12 ms | 0.02% | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[20.6](/docs/network/latency/pairs/mrs-ber-rtt)**  | 11.62 ms    | 56.4%      | 0.24 ms | 0%    | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[27.5](/docs/network/latency/pairs/mow-ber-rtt)**  | 15.8 ms     | 57.5%      | 0.3 ms  | 0.13% | Ultra-Low |
| 🇺🇸 New York (NYC)     | **[78.8](/docs/network/latency/pairs/nyc-ber-rtt)**  | 62.7 ms     | 79.6%      | 0.67 ms | 0%    | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[86.1](/docs/network/latency/pairs/iad-ber-rtt)**  | 66.05 ms    | 76.7%      | 0.7 ms  | 0%    | Good      |
| 🇺🇸 Miami (MIA)        | **[117.3](/docs/network/latency/pairs/mia-ber-rtt)** | 78.44 ms    | 66.9%      | 1.4 ms  | 0%    | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[139.3](/docs/network/latency/pairs/lax-ber-rtt)** | 91.39 ms    | 65.6%      | 1.58 ms | 0.12% | Good      |
| 🇺🇸 Seattle (SEA)      | **[140.9](/docs/network/latency/pairs/sea-ber-rtt)** | 79.73 ms    | 56.6%      | 1.36 ms | 0.01% | Good      |
| 🇭🇰 Hong Kong (HKG)    | **[145.1](/docs/network/latency/pairs/hkg-ber-rtt)** | 85.85 ms    | 59.2%      | 0.83 ms | 0.18% | Good      |
| 🇹🇼 Taipei (TPE)       | **[158.6](/docs/network/latency/pairs/tpe-ber-rtt)** | 87.84 ms    | 55.4%      | 1.84 ms | 0.09% | Fair      |
| 🇸🇬 Singapore (SIN)    | **[160.3](/docs/network/latency/pairs/sin-ber-rtt)** | 97.19 ms    | 60.6%      | 0.88 ms | 0.19% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[172.1](/docs/network/latency/pairs/jnb-ber-rtt)** | 86.53 ms    | 50.3%      | 1.75 ms | 0.11% | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[186.1](/docs/network/latency/pairs/tyo-ber-rtt)** | 87.53 ms    | 47%        | 1.64 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[191.3](/docs/network/latency/pairs/gru-ber-rtt)** | 100.2 ms    | 52.4%      | 2.12 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[254.7](/docs/network/latency/pairs/mel-ber-rtt)** | 156.34 ms   | 61.4%      | 1.95 ms | 0%    | High      |
| 🇦🇺 Sydney (SYD)       | **[260.5](/docs/network/latency/pairs/syd-ber-rtt)** | 157.54 ms   | 60.5%      | 2.14 ms | 0%    | 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-amsterdam) | AMS  | Netherlands | **7.2**  | Ultra-Low |
| [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA  | Germany     | **6.1**  | Ultra-Low |
| [🇬🇧 London (LON)](./lon-london)       | LON  | UK          | **15.2** | Ultra-Low |
| [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS  | France      | **20.2** | Ultra-Low |
| [🇷🇺 Moscow (MOW)](./mow-moscow)       | MOW  | Russia      | **28.6** | Ultra-Low |
| [🇫🇷 Paris (PAR)](./par-paris)         | PAR  | France      | **15.6** | Ultra-Low |

## Frequently Asked Questions

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

The fastest measured route to Berlin (BER) is [Frankfurt (FRA) → Berlin (BER)](/docs/network/latency/pairs/fra-ber-rtt), 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)](/docs/network/latency/pairs/ber-fra-rtt), 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)](/docs/network/latency/pairs/ber-syd-rtt), averages **262.1 ms** RTT.

## Open Data

Measured latency data for Berlin (BER) 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 Berlin is published as `ber-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [ber-fra.pings.csv](/opendata/latency/latest/pairs/ber-fra.pings.csv), the 50-probe ICMP echo round for [Berlin (BER) → Frankfurt (FRA)](/docs/network/latency/pairs/ber-fra-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/ber-berlin).
- **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.