KATHMANDU · Nepal
PeeringDB records one internet exchange in Kathmandu, npIX DH, filed in full as Internet Exchange Nepal, with 30 participants. Six colocation facilities are on record and only two of them report a network each. An address geolocating to Kathmandu reflects the location an operator published for a block, not the position of a device.
Internet exchanges in KATHMANDU
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 |
|---|---|---|
npIX DH Internet Exchange Nepal | 30 | 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 |
|---|---|---|
| Dataspace Kathmandu | 1 | Dream Homes, Putalisadak - Kamaladi Crossing Kathmandu |
| Ncell IDC - KTM1 - Kathmandu | 1 | Nakkhu |
| Subisu Ltd. | 0 | Baluwatar Baluwatar |
| Nepal Digital Service Pvt Ltd | 0 | Gangbu Kathmandu |
| Data Hub Nepal | 0 | 2nd Floor, Shikhar Biz Center Thapathali |
| Data World KTM-M-DC-01 | 0 | Buathali, Matatirtha Chandragiri |
What a KATHMANDU IP address tells you
npIX DH is the only exchange PeeringDB lists in Kathmandu, and its 30 participants account for the whole of the city's recorded peering population. Colocation adds almost nothing to that number. Of the six facilities on record, Dataspace Kathmandu and Ncell IDC - KTM1 - Kathmandu report one network each, while Subisu Ltd., Nepal Digital Service Pvt Ltd, Data Hub Nepal and Data World KTM-M-DC-01 report none, so the documented capacity sits at the exchange rather than across carrier-neutral buildings. No carrier ASN is attached to npIX DH, and the carrier data behind this page holds no Nepali mobile operator to match against it.
An address that a database places in Kathmandu need not be a device in Kathmandu. An operator announces a block from a registry record that carries one address for the entire allocation, often the operator's own office rather than the customer. Mobile traffic leaves a network through a small number of gateways that can sit well away from the subscriber. Geolocation providers read the location the operator published and repeat it, so a connection from another part of Nepal still resolves to Kathmandu in most lookups.
Anyone checking an address learns more from the origin ASN and the netname on the specific prefix than from the city label. The ASN names the network announcing the block, and the netname with its registry entry shows who holds the range and which address that holder chose to publish. Where the two disagree, the city label is the weaker source. Against the 30 networks at npIX DH, an announcing ASN that appears nowhere in Kathmandu's records has no documented presence in the city.
Questions
Which internet exchanges are in Kathmandu?
One. PeeringDB records npIX DH, listed in full as Internet Exchange Nepal, with 30 participants. No second exchange appears for the city. Six colocation facilities are also on record, and of those only Dataspace Kathmandu and Ncell IDC - KTM1 - Kathmandu report a network, one each.
Do Nepal mobile carriers peer in Kathmandu?
The registry does not say. npIX DH has no carrier ASNs attached to it, and the carrier data behind this page holds no mobile operator ASNs for Nepal, so there is nothing on record either way. That silence is missing data, not evidence that no mobile network peers in the city.
Does an IP that geolocates to Kathmandu mean the device is there?
No. Geolocation databases follow the location an operator publishes for an address block, and one record can cover addresses in use across the country. Mobile traffic exits through a few gateways, so a Kathmandu label describes the operator's registration more closely than it describes the handset.
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