Ulaanbaatar · Mongolia
PeeringDB records three internet exchanges in Ulaanbaatar and no colocation facilities. MISPA-IXP is the best connected with 13 participants, MIX MNDC has 8, and IXP-MN has none listed. No mobile carrier ASN appears at any of them, so an address geolocating to the city reflects an operator's registration rather than a device position.
Internet exchanges in Ulaanbaatar
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 |
|---|---|---|
MISPA-IXP MISPA internet exchange point | 13 | none in the registry |
MIX MNDC Mongolian Internet Exchange & Mongolian National Data Center | 8 | none in the registry |
IXP-MN | 0 | none in the registry |
Exchange records: PeeringDB.
What a Ulaanbaatar IP address tells you
MISPA-IXP carries 13 of the 21 peering records PeeringDB holds for Ulaanbaatar, and MIX MNDC, the Mongolian Internet Exchange and Mongolian National Data Center, accounts for the remaining eight. A third entry, IXP-MN, carries no participants and no long name, so it adds nothing to the count. PeeringDB lists no colocation facilities in the city and no networks inside them, which puts every documented connection at an exchange rather than in a carrier-neutral building. The registry attaches no carrier ASN to any of the three exchanges.
An address a database places in Ulaanbaatar need not be a device in Ulaanbaatar. Operators announce address blocks from a registry record that carries one address for a whole allocation, and mobile traffic leaves through a small number of gateways that can sit far from the subscriber. Geolocation providers read the operator's published location and repeat it, so a connection from elsewhere in Mongolia can still resolve to Ulaanbaatar. PeeringDB names no mobile ASNs for the country in this record, so nothing in the city entry ties an address to a carrier's own peering presence.
Someone checking an address gets more from the origin ASN and the netname on the specific prefix than from the city label. The ASN says which network announced the block, the netname says which allocation it belongs to, and neither depends on a geolocation vendor's estimate. Because PeeringDB shows no carrier ASNs at MISPA-IXP or MIX MNDC, a Mongolian mobile prefix cannot be matched to a peering record in the city, and whether traffic crossed either exchange stays outside what a city lookup answers.
Questions
Which internet exchanges are in Ulaanbaatar?
PeeringDB lists three. MISPA-IXP records 13 participants, MIX MNDC records 8, and IXP-MN records none. Those counts cover the networks the registry knows about at each exchange, so peering arranged privately between two networks does not appear in them.
Do Mongolia mobile carriers peer in Ulaanbaatar?
The registry attaches no carrier ASNs to MISPA-IXP, MIX MNDC or IXP-MN, and it names no Mongolian mobile operators for the city at all. That is silence in the record rather than proof that no operator exchanges traffic in Ulaanbaatar.
Does an IP that geolocates to Ulaanbaatar mean the device is there?
No. The city label comes from the address block's registration and the operator's published location, not from the device. A subscriber elsewhere in Mongolia can leave through a gateway whose addresses are registered in Ulaanbaatar and will appear there in every database copying that record.
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