Dushanbe · Tajikistan
PeeringDB records one internet exchange in Dushanbe, TJ-IX, with 17 participating networks, and one colocation facility, NKT-HUB, listing 3 networks. TJ-IX is the best connected exchange in the city. An address that geolocates to Dushanbe shows where an operator registered the block, not where a device sits.
Internet exchanges in Dushanbe
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 |
|---|---|---|
TJ-IX TJ-IX Dushanbe | 17 | 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 |
|---|---|---|
| NKT-HUB | 3 | 5b, Mirzo Mastangulov st. |
What a Dushanbe IP address tells you
Dushanbe's public peering runs through a single exchange. TJ-IX, listed in PeeringDB as TJ-IX Dushanbe, has 17 participant networks, and that count is the whole of the city's recorded exchange peering. The one colocation facility on record, NKT-HUB, lists 3 networks, so most of what the registry documents sits at the exchange rather than spread across separate buildings. PeeringDB attaches no carrier ASNs to TJ-IX, and the carrier registry holds no Tajik mobile operator entries, so the data does not show a mobile network peering here.
An address that a database places in Dushanbe may belong to a device somewhere else in Tajikistan. Operators receive address blocks as registry records and announce them from wherever their routers sit, and one record can cover a whole national network. Mobile traffic in particular leaves through a small number of gateways, so handsets across a wide area can appear behind the same city. Geolocation databases usually take the operator's own published location for a block, which means they repeat the address on the registry entry rather than measuring where the traffic starts.
Someone checking an address is better off reading the origin ASN and the netname on the specific prefix than trusting a city label. The origin ASN says which network announces the block, and the netname and registry record say who holds it and what area they registered it for. With 17 networks at TJ-IX and 3 at NKT-HUB, the set of candidate origins in Dushanbe is small enough to look at directly.
Questions
Which internet exchanges are in Dushanbe?
PeeringDB records one, TJ-IX, listed as TJ-IX Dushanbe, with 17 participant networks. No second exchange appears for the city in the registry. The one colocation facility on record, NKT-HUB, lists 3 networks.
Do Tajikistan mobile carriers peer in Dushanbe?
The registry does not show it. PeeringDB attaches no carrier ASNs to TJ-IX, and the carrier registry holds no mobile operator entries for Tajikistan. That silence is a gap in the data rather than proof that no mobile network connects in the city.
Does an IP that geolocates to Dushanbe mean the device is there?
No. The city label comes from the address block's registry record and the operator's published location, not from a measurement. A network can announce a Dushanbe-registered block from anywhere it runs routers, and mobile subscribers across Tajikistan can exit through gateways carrying the same city.
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