Hamburg · Germany
PeeringDB records four exchanges in Hamburg, Germany, and 22 facilities holding 214 network presences. DE-CIX Hamburg is the best connected with 167 participants, followed by MegaIX Hamburg with 55. An address that geolocates to Hamburg tells you which operator registered the block, not where a device using it sits.
Internet exchanges in Hamburg
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 |
|---|---|---|
DE-CIX Hamburg | 167 | |
MegaIX Hamburg Megaport MegaIX Hamburg | 55 | |
CSNIX - Hamburg | 1 | none in the registry |
CSNIX - Hamburg RemotePeering | 0 | 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 |
|---|---|---|
| Portus/IPHH HH2 (Wendenstrasse 408) | 41 | Wendenstraße 408 |
| GlobalConnect Hamburg (HAM2) | 40 | Wendenstrasse 379 |
| NorthC Hamburg | 18 | Süderstrasse 198 |
| Portus/IPHH HH3 (Wendenstrasse 251) | 17 | Wendenstraße 251 |
| n@work Hamburg Wendenstraße | 15 | Wendenstr. 379 20537 Hamburg |
| GlobalConnect Hamburg (HAM1) | 15 | Flughafen Strasse 54a |
| GlobalConnect Hamburg (HAM3) | 12 | Wendenstr. 255 |
| euNetworks Colocation Hamburg | 10 | Wendenstraße 408 |
| NTT Hamburg 1 Data Center (HAM1) | 8 | Langenhorner Chaussee 40 |
| Artfiles w408 | 8 | Wendenstrasse 408 |
| AtlasEdge DC Hamburg HAM001 | 5 | Obenhauptstr. 1c |
| Equinix HH1 - Hamburg | 5 | Vierenkamp 1 |
Showing the 12 facilities with the most networks, of 22 recorded.
What a Hamburg IP address tells you
DE-CIX Hamburg holds most of the city's exchange peering with 167 participants, and MegaIX Hamburg adds 55, while the two CSNIX Hamburg listings record one participant and none. Facility presences run to 214 across 22 sites, spread thinly rather than concentrated, with Portus/IPHH HH2 at 41 networks, GlobalConnect Hamburg HAM2 at 40 and NorthC Hamburg at 18. O2 (AS6805) peers on MegaIX Hamburg, and PeeringDB does not list Deutsche Telekom or Vodafone mobile ASNs on a Hamburg exchange.
A Hamburg geolocation result is a statement about an address block, not about a handset. Operators announce prefixes from registry records that carry one address for the whole allocation, and mobile traffic in Germany exits through a small number of gateways, which detaches the reported city from the user's actual cell. Databases that answer geolocation queries copy the operator's published location, so they repeat what the operator filed rather than measuring anything.
Someone verifying a Hamburg address should read the origin ASN and the netname on the specific prefix. The ASN distinguishes mobile ranges, including O2's AS6805, from the hosting networks that fill the 214 facility presences recorded in the city. The registry entry on the prefix shows the size and purpose of the allocation, which the city field in a geolocation database cannot.
Mobile carriers in Germany
A mobile address in Hamburg 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 Hamburg?
PeeringDB records four. DE-CIX Hamburg has 167 participants and MegaIX Hamburg has 55. The other two, CSNIX - Hamburg and its remote peering listing, show one participant and zero. The city also has 22 facilities holding 214 network presences.
Do German mobile carriers peer in Hamburg?
O2 (AS6805) is listed on MegaIX Hamburg. Deutsche Telekom (AS3320) and Vodafone (AS3209) mobile ASNs do not appear on Hamburg exchanges in PeeringDB, so their traffic to the city runs over transit or private connections instead.
Does an IP that geolocates to Hamburg mean the device is there?
No. Geolocation follows the location an operator publishes for the address block, and mobile subscribers are routed through few gateways. A Hamburg answer narrows down the network that announces the prefix, not the position of the device using it.
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