Zaventem · Belgium
PeeringDB records no internet exchange in Zaventem. Five colocation facilities hold 50 network presences between them, with brusselsdc at 15 and Digital Realty BRU3 at 14. Nothing in the registry ties an address to the town itself, so a Zaventem geolocation reflects an operator's paperwork rather than a device location.
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 |
|---|---|---|
| brusselsdc | 15 | Excelsiorlaan 15 |
| Digital Realty BRU3 - Brussels | 14 | Mercuriusstraat 27 |
| Unix-Solutions DC Zaventem | 13 | Hoge Wei 37 |
| Digital Realty BRU4 - Brussels | 6 | Mercuriusstraat 27 |
| EXA Edge DC Zaventem | 2 | Leuvensesteenweg 573 1930 Zaventem |
What a Zaventem IP address tells you
Zaventem has no exchange in PeeringDB, so its recorded connectivity sits entirely in colocation. Five facilities hold 50 network presences, with brusselsdc at 15, Digital Realty BRU3 at 14, Unix-Solutions DC Zaventem at 13, Digital Realty BRU4 at 6 and EXA Edge DC Zaventem at 2. Those are modest counts next to the 182 presences the registry records in Brussels, and no Belgian mobile operator appears in the carrier registry, so the data shows no mobile network peering in the town. Networks here reach each other over private links and through exchanges recorded elsewhere.
An address that geolocates to Zaventem may belong to a device anywhere on the announcing network. An operator registers an address block once, with one postal address, and that address can be an office or a national contact point rather than the place a subscriber sits. Mobile networks make the distance larger still, because traffic from across the country leaves through a handful of gateways and inherits whichever block those gateways announce. Geolocation providers copy the operator's published location, so a town-level answer can be an administrative artefact.
Check the routing record rather than the town name. The origin ASN identifies the network announcing the prefix, and the netname on that prefix shows how its holder describes the range and how wide the announcement is. Where an operator announces one block for a whole country, no city or town inside it means much on its own. The 50 network presences PeeringDB records across the five Zaventem facilities are the operators with equipment in the town, which is a much shorter list than the addresses geolocating to it.
Questions
Is there an internet exchange in Zaventem?
PeeringDB records none. The town's entry holds five colocation facilities and no exchange point, so networks with equipment there peer privately or over exchanges recorded in other places. The registry can only be read for what it lists, and it lists no Zaventem exchange.
Which data centres does PeeringDB list in Zaventem?
Five: brusselsdc with 15 networks, Digital Realty BRU3 with 14, Unix-Solutions DC Zaventem with 13, Digital Realty BRU4 with 6 and EXA Edge DC Zaventem with 2. Together they account for 50 network presences in the town.
Does an IP that geolocates to Zaventem mean the device is there?
No. Geolocation databases follow the location an operator published for the address block, and one block often covers a national footprint. Look at the origin ASN and the netname on the specific prefix to see who announces the range and how broadly it is used.
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