Berlin · Germany
PeeringDB records four exchanges in Berlin, Germany, and 18 facilities holding 343 network presences against 230 exchange peering records. BCIX, the Berlin Commercial Internet Exchange, is the best connected with 141 participants. An address that geolocates to Berlin reflects an operator's registry record and gateway design rather than a device's position.
Internet exchanges in Berlin
An exchange is a shared switch where networks hand traffic to each other directly. Participant counts come from PeeringDB, where each network maintains its own record.
| Exchange | Participants | Registry carriers peering |
|---|---|---|
BCIX Berlin Commercial Internet Exchange | 141 | |
MegaIX Berlin Megaport MegaIX Berlin | 43 | none in the registry |
BGP.Exchange - Berlin | 40 | none in the registry |
FIX Berlin the Fr(ickel|ee|ei|eundlich) Internet Exchange, Berlin | 6 | none in the registry |
Exchange records: PeeringDB.
Colocation facilities
Buildings where networks put equipment. The network count is how many PeeringDB members list a presence there, which shows where capacity in the city sits.
| Facility | Networks present | Address |
|---|---|---|
| CarrierColo Berlin Luetzow (I/P/B/ site B) | 104 | Lützowstrasse 105/106 |
| NTT Berlin 1 Data Center (BER1) | 61 | Nonnendammallee 15 |
| Speedbone Berlin | 44 | Alboinstr. 36 - 42 Alboin-Kontor |
| NorthC Berlin | 28 | Gradestrasse 60 |
| euNetworks Colocation Berlin | 25 | Alboinstrasse 36-42 Alboin-Kontor |
| CarrierColo Berlin Kitzing (I/P/B/ site K) | 15 | Kitzingstr. 15 |
| 3U Rechenzentrum Berlin | 14 | Lorenzweg 5 |
| NTT Berlin 2 Data Center (BER2) | 11 | Lankwitzer Strasse 45-47 |
| DNS:NET Colo I Berlin | 10 | Lützowstr. 105 |
| AtlasEdge DC Berlin BER001 | 8 | Wiebestr. 46 |
| Penta Infra Berlin BER01 | 8 | Florastr. 133 12623 Berlin |
| Datacenter Berlin Mahlsdorf (RZB) - PŸUR Business | 5 | Florastraße 133 - 136 |
Showing the 12 facilities with the most networks, of 18 recorded.
What a Berlin IP address tells you
Berlin's exchange traffic concentrates on BCIX, which lists 141 participants, ahead of MegaIX Berlin at 43, BGP.Exchange - Berlin at 40 and FIX Berlin at 6. More network presences sit in colocation than on the exchanges, 343 across 18 facilities against 230 peering records, headed by CarrierColo Berlin Luetzow with 104 networks, NTT Berlin 1 with 61 and Speedbone Berlin with 44. Vodafone (AS3209) and O2 (AS6805) both peer at BCIX, and PeeringDB does not record Deutsche Telekom's mobile ASN 3320 on a Berlin exchange.
An address that geolocates to Berlin does not place a device in Berlin. An operator announces a prefix from a registry record with a single administrative address, and German mobile networks send subscriber traffic out through a handful of gateways, so one city label can cover users spread across the country. Geolocation databases take the operator's published location for the block, so the city they report is the one the operator wrote down.
Checking the origin ASN answers more than the city field. On a Berlin address it shows whether the prefix comes from a mobile network such as Vodafone (AS3209) or O2 (AS6805), or from one of the hosting networks behind the 343 presences in Berlin facilities. The netname and the registry entry on that exact prefix say what the range was allocated for and how wide the assignment runs.
Mobile carriers in Germany
A mobile address in Berlin is routed by one of the country's operators. Each entry lists the operator's ASNs, so you can check which network an address belongs to.
Questions
Which internet exchanges are in Berlin?
Four. BCIX, the Berlin Commercial Internet Exchange, has 141 participants. MegaIX Berlin has 43, BGP.Exchange - Berlin has 40 and FIX Berlin has 6. Berlin also holds 18 colocation facilities with 343 network presences between them.
Do German mobile carriers peer in Berlin?
Vodafone (AS3209) and O2 (AS6805) are listed on BCIX. PeeringDB does not record Deutsche Telekom's mobile ASN 3320 on a Berlin exchange. Peering in a city says where an operator exchanges traffic, not where its subscribers connect.
Does an IP that geolocates to Berlin mean the device is there?
No. The city comes from the operator's own record for the address block, and mobile traffic leaves through few gateways. Treat a Berlin result as information about the network that announces the prefix rather than about the device's location.
Sources
- PeeringDB - exchanges, participant counts, facilities and network presence, snapshot 2026-09-07
- PROXIES.SX carrier and ASN registry - operator ASNs used to match peering participants