Arequipa · Peru
PeeringDB records one exchange in Arequipa, PIT - Peru - Arequipa, with 14 participants, and two facilities, Internexa Arequipa - Socabaya with a single network and PIT Peru Arequipa - AQP1 with none. Peer records for the city total 14. An IP that geolocates to Arequipa reflects an operator's registry entry rather than the position of a device.
Internet exchanges in Arequipa
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 |
|---|---|---|
PIT - Peru - Arequipa anteriormente Peru IX Arequipa | 14 | 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 |
|---|---|---|
| Internexa Arequipa - Socabaya | 1 | Calle Sub-estación |
| PIT Peru Arequipa - AQP1 | 0 | Calle Jacinto Ibañez 148 |
What a Arequipa IP address tells you
The recorded capacity in Arequipa sits in one exchange. PIT - Peru - Arequipa carries 14 participants, and that number matches the city's total of 14 peer records, so the data shows no interconnection outside it. Colocation adds almost nothing. Internexa Arequipa - Socabaya lists a single network and PIT Peru Arequipa - AQP1 lists none, which leaves one facility network for the whole city. The exchange record flags no participant as a carrier ASN, and the carrier registry holds no mobile operator ASNs for Peru.
A database that places an address in Arequipa is reading a registry record, not measuring a device. Networks register blocks at a company address and announce them from routers that may sit elsewhere, so a national operator can hand an Arequipa-registered range to subscribers in another region without changing anything a lookup can see. Mobile addresses compress further, since handsets reach the internet through a handful of gateways and the geolocation entry follows whatever location the operator publishes for the block.
With one exchange and one facility network on record, Arequipa gives little to corroborate a city claim, so the origin ASN and the netname on the exact prefix carry the weight. They name the network announcing the address and the organisation the block is registered to. Checking whether that ASN sits among the 14 participants at PIT - Peru - Arequipa tells you whether the network has any documented interconnection in the city at all, and a network that appears nowhere in the local record leaves only its own registration behind the label.
Questions
Which internet exchanges are in Arequipa?
PeeringDB records one, PIT - Peru - Arequipa, with 14 participants. Two facilities appear alongside it, Internexa Arequipa - Socabaya with one network present and PIT Peru Arequipa - AQP1 with none recorded, so the exchange accounts for the city's interconnection.
Do Peru mobile carriers peer in Arequipa?
The exchange record flags no participant as a carrier ASN, and the carrier registry contains no mobile operator ASNs for Peru, so the data cannot answer this either way. That absence means the registry is silent, not that no operator connects in the city.
Does an IP that geolocates to Arequipa mean the device is there?
No. Geolocation databases take the location an operator publishes for an address block, so an address can read Arequipa while the traffic behind it starts elsewhere in the same network. The routing data and the prefix's own registration describe where the block is announced.
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