Seongnam · South Korea
PeeringDB records no internet exchange in Seongnam. Four colocation facilities carry 15 networks between them, and KINX Bundang holds the most at eight, followed by Hostway Seoul and SKbroadbandidc with three each and kt cloud Bundang with one. An address that geolocates to Seongnam points at an operator's registration rather than a device's position.
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 |
|---|---|---|
| KINX Bundang | 8 | 36, Jangmi-ro, Bundang-gu |
| Hostway Seoul | 3 | 343-1 Yatap-dong Bundang-gu |
| SKbroadbandidc | 3 | 12, Seongnam-daero 2beon-gil Bundang-gu |
| kt cloud Bundang | 1 | 36, Seongnamdaero 925beongil Bundang-gu, Seongnam-si, Gyeonggi-do |
What a Seongnam IP address tells you
Seongnam has no exchange in the PeeringDB record and no participant count to go with one, so everything documented in the city sits in colocation. Four facilities report 15 networks: KINX Bundang with eight, Hostway Seoul and SKbroadbandidc with three each, and kt cloud Bundang with one. Networks in those buildings either peer privately or carry their traffic to an exchange elsewhere, since the registry places none in Seongnam. No carrier ASN is attached to the city, so the record names no South Korean mobile operator peering here.
An address that a database places in Seongnam need not be a device in Seongnam. Operators announce address blocks from a registry record that carries a single address for an allocation covering a far wider area, and mobile traffic leaves through a handful of gateways whose location has little to do with the subscriber. Geolocation databases follow the operator's own published location, so a connection made in another city can resolve to Seongnam because that is the address on the paperwork.
The origin ASN and the netname on the specific prefix tell you more than the city field does. They show whether the block belongs to a mobile network, a fixed-line operator or a customer of one of the four facilities on record, and how large the registered allocation is. A count of 15 networks across those buildings says nothing about which of them, if any, answers for a given address.
Questions
Which internet exchanges are in Seongnam?
None. PeeringDB records no exchange in Seongnam, only four colocation facilities holding 15 networks. Networks in the city that want public peering connect at an exchange in another location, and the registry does not record where they do so.
Do South Korea mobile carriers peer in Seongnam?
The registry attaches no carrier ASNs to Seongnam, and with no exchange in the city there is no participant list to check them against. Mobile operators may still hold space in the four facilities on record without that appearing in PeeringDB.
Does an IP that geolocates to Seongnam mean the device is there?
No. The label comes from the registration on the address block and the operator's published location. A device connected somewhere else in South Korea can use addresses registered to Seongnam, and every database copying that registration will report Seongnam.
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