Kota Bandung · Indonesia
PeeringDB records no internet exchange in Kota Bandung and three facilities holding 104 network presences between them. neuCentrIX - Bandung is the best connected of the three at 64 networks, ahead of APJII Jabar at 38. An address that geolocates here reports the location an operator published for the block, not where a device sits.
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 |
|---|---|---|
| neuCentrIX - Bandung | 64 | neuCentrIX Lembong; Jl. Lembong No.11, Braga, Kec. Sumur Bandung, Kota Bandung, Jawa Barat 40111 |
| APJII Jabar | 38 | Gedung Wisma Bumiputera, Lantai 8 Suite #806C Jl. Asia Afrika No.141-149, Kec. Sumur Bandung |
| XLSmart Bandung (BNB) | 2 | Jalan Soekarno Hatta 779 Cisaranten Kulon |
What a Kota Bandung IP address tells you
Kota Bandung has no exchange record in PeeringDB, so the capacity the registry documents sits in colocation. Three facilities hold 104 network presences between them. neuCentrIX - Bandung accounts for 64 of those, APJII Jabar for 38, and XLSmart Bandung (BNB) for the remaining 2. With no exchange listed, PeeringDB reports no peers for the city, and networks in those buildings that peer publicly do so under records filed for somewhere else. No mobile carrier ASN appears on any of the three facility records.
An address that geolocates to Kota Bandung reflects a registry record its operator published, not the position of the hardware using it. Networks announce ranges from a registration that can cover the whole country, and mobile traffic leaves through a small number of gateways, so a handset connected in another city can present an address that databases place here. Geolocation providers read the operator's own published location and inherit whatever that record says, which is why a city field can stay fixed while the equipment behind it moves.
The origin ASN and the netname on the specific prefix say more than the city label does. They name the network announcing the block and the party that registered it, and neither has to sit in Kota Bandung. Where a prefix traces back to one of the three facilities listed here, the building is a closer read on position than a city field, though the 104 network presences recorded belong to operators whose footprints run past the city.
Questions
Which internet exchanges are in Kota Bandung?
PeeringDB lists none. What the city has on record is three colocation facilities: neuCentrIX - Bandung with 64 networks, APJII Jabar with 38, and XLSmart Bandung (BNB) with 2, for 104 network presences in total. Networks in those buildings may still peer at exchanges recorded under other cities.
Do Indonesian mobile carriers peer in Kota Bandung?
The snapshot does not say. No mobile carrier ASN is attached to the city's three facility records, and with no exchange listed there is no participant list to check against. That silence is a gap in what the registry documents rather than proof that no carrier is present.
Does an IP that geolocates to Kota Bandung mean the device is there?
No. The city label comes from the location an operator published for the address block, and mobile subscribers reach the internet through gateways that can sit far from where they are. Check the origin ASN and the netname on the prefix rather than the city field.
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