Aqaba · Jordan
PeeringDB records one exchange in Aqaba. Aqaba IX has 19 participants, and two colocation facilities hold six network presences between them, five at NaiTel Aqaba and one at iLevant Aqaba. An address that geolocates to Aqaba shows where an operator registered the block, not where a device sits.
Internet exchanges in Aqaba
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 |
|---|---|---|
Aqaba IX | 19 | 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 |
|---|---|---|
| NaiTel Aqaba | 5 | King Abduallah st. 41 |
| iLevant Aqaba | 1 | King Abdullah St. 41 |
What a Aqaba IP address tells you
All of Aqaba's exchange peering sits on one fabric. Aqaba IX carries 19 participants, and no second exchange appears in the city's records. Colocation is smaller by comparison, with two facilities holding six network presences between them, five of those at NaiTel Aqaba and one at iLevant Aqaba. Aqaba IX lists no mobile carrier ASN among its participants, and the carrier registry holds no mobile ASN for a Jordanian operator, so the exchange records cannot show whether any of them peer in the city.
A database can place an address in Aqaba while the network announcing it works from somewhere else in Jordan. Operators register address blocks against a company record, and that record carries the company's own address rather than the location of the equipment using the block. Mobile traffic widens the gap, because a carrier routes large subscriber pools through a small number of gateways, and everyone behind one gateway shares its public address wherever the handset happens to be. Geolocation databases read what the operator published, so they repeat the operator's choice rather than measuring the device.
The origin ASN on the specific prefix answers more than a city label does. The netname and the registered holder show which company the block belongs to, and a block registered to one of the facility operators on the Aqaba list, NaiTel or iLevant, points at hosting rather than a handset on a mobile network. Checking whether that origin ASN appears among the 19 participants on Aqaba IX shows whether the network peers locally at all. Where the registry says nothing about a mobile operator, the prefix record is the only public evidence left.
Questions
Which internet exchanges are in Aqaba?
PeeringDB lists one, Aqaba IX, with 19 participants. No second exchange appears in the city's record. Two colocation facilities sit alongside it, NaiTel Aqaba with five network presences and iLevant Aqaba with one, six across the pair.
Do Jordan mobile carriers peer in Aqaba?
The records do not say. Aqaba IX lists no mobile carrier ASN among its 19 participants, and the carrier registry holds no mobile ASN for any Jordanian operator, so there is nothing to match the participant list against. Absence here is missing data, not proof.
Does an IP that geolocates to Aqaba mean the device is there?
No. Geolocation databases follow the address an operator published on its registry record, and mobile networks route many subscribers through a few gateways, so one public address can stand for handsets far from the city. The origin ASN and netname on the prefix say more.
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