Antwerp · Belgium
PeeringDB records no exchange in Antwerp. Six colocation facilities hold 39 network presences between them, with antwerpdc at 17 and LCL Antwerp at 15 accounting for most of that. The registry lists no Belgian mobile operator, so an Antwerp geolocation says how an address block was registered rather than where a device is.
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 |
|---|---|---|
| antwerpdc | 17 | Häifastraat 6 |
| LCL Antwerp | 15 | Noorderlaan 133 |
| Hermes Telecom DC | 4 | Noorderlaan 147 bus 22 51.264163, 4.399468 |
| dcvlaanderen | 3 | noorderlaan 147 bus 32 |
| Versatel Antwerp | 0 | Noorderlaan 113 |
| EXA Edge DC Antwerp | 0 | 20 Antwerpsebaan |
What a Antwerp IP address tells you
Antwerp's capacity in PeeringDB sits in colocation, not at an exchange. Six facilities hold 39 network presences, and two of them carry most of the total: antwerpdc has 17 and LCL Antwerp has 15, with Hermes Telecom DC at 4 and dcvlaanderen at 3. Versatel Antwerp and EXA Edge DC Antwerp have no networks recorded. The city has no exchange point in the registry, so networks here interconnect privately or over exchanges listed in other cities, and no Belgian mobile operator ASN appears in the carrier registry for the city.
An address that geolocates to Antwerp does not fix a device in Antwerp. Operators announce address blocks from a registry record that carries one location for the whole range, and that location is chosen by the holder, not measured. Mobile networks concentrate their exits in a few gateways, so subscribers spread over a wide area share the addresses those gateways announce. Geolocation databases follow the operator's own published location, which means a city-level answer can describe a filing rather than a place where hardware runs.
The useful checks are on the prefix itself. The origin ASN names the network announcing it, and the netname and registered holder on that prefix show whether the block belongs to a local operator or to a national range that happens to carry an Antwerp label. A single announcement covering a country tells you nothing about a city inside it. The 39 network presences PeeringDB records across the six Antwerp facilities are the networks with equipment in the city, and that list is separate from the addresses that geolocate to it.
Questions
Which internet exchanges are in Antwerp?
PeeringDB lists none for Antwerp. The city's entry contains six colocation facilities and no exchange point, so networks with equipment there peer privately or at exchanges recorded in other cities. The registry is silent on any Antwerp exchange rather than ruling one out.
Do Belgian mobile carriers peer in Antwerp?
The carrier registry holds no Belgian mobile operator ASNs, and Antwerp has no exchange in PeeringDB, so there is no peering record to read. That is a gap in the data, not evidence that mobile networks avoid the city.
Does an IP that geolocates to Antwerp mean the device is there?
No. The answer comes from the location an operator published for the address block, which can cover a region or a country. Read the origin ASN and the netname on the exact prefix to see who announces it and how wide the announcement runs.
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