Meppel · Netherlands
PeeringDB records one internet exchange in Meppel, LOCIX NETHERLANDS, with 48 participants, and one colocation facility, KoloDC NL2, listing 51 networks. LOCIX NETHERLANDS is the only exchange here and the best connected by participant count. An address that geolocates to Meppel says where a network registered the block, not where a device sits.
Internet exchanges in Meppel
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 |
|---|---|---|
LOCIX NETHERLANDS LOCIX EXCHANGE NETHERLANDS | 48 | 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 |
|---|---|---|
| KoloDC NL2 | 51 | Ketelskamp 10 |
What a Meppel IP address tells you
Meppel's entry in PeeringDB is short. One exchange, LOCIX NETHERLANDS, carries 48 participants, and one colocation facility, KoloDC NL2, lists 51 networks. Almost everything the registry records for the city sits in that one building, and the two counts differ by three, so the exchange and the facility describe close to the same set of networks. PeeringDB attaches no carrier ASNs to LOCIX NETHERLANDS, which means no mobile operator appears among the networks the registry places at the exchange.
An address that a database places in Meppel is often not a device in Meppel. A network registers an address block once, with one location in the RIR record, then announces it from wherever its routers are; a block filed to a Meppel office can be used across the whole country. Mobile traffic compounds this, because operators push subscriber sessions through a handful of gateways and every session behind a gateway inherits its address. Geolocation databases mostly copy the operator's published location, so they repeat the registry rather than measure the phone.
Reading the address itself gets further than reading a city label. Look up the origin ASN for the exact prefix and check whether that network is one of the 48 participants at LOCIX NETHERLANDS or one of the 51 networks recorded at KoloDC NL2; if it is neither, the traffic has no recorded reason to touch Meppel. The netname and the registered holder on the prefix tell you which operator holds it, and a mobile operator's block reads differently from a hosting or colocation block.
Questions
Which internet exchanges are in Meppel?
PeeringDB lists one, LOCIX NETHERLANDS, recorded in full as LOCIX EXCHANGE NETHERLANDS, with 48 participants. It is the only exchange the registry places in the city, so it is also the best connected one there by participant count.
Do Dutch mobile carriers peer in Meppel?
The registry does not say so. PeeringDB attaches no carrier ASNs to LOCIX NETHERLANDS, and no mobile operator appears in the city's records here. That is an absence of evidence rather than proof; a carrier could reach Meppel over a private link that PeeringDB never lists.
Does an IP that geolocates to Meppel mean the device is there?
No. The city label comes from the location an operator filed with its address block and from geolocation databases that copy that filing. The block can be announced anywhere the operator has routers, and mobile sessions take the address of the gateway they leave through.
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