Ankara · Turkey
PeeringDB records a single exchange in Ankara, Turkey. RegPEX has 5 participants, and the city's seven colocation facilities hold 25 network presences between them, with Mars Datacenter Ankara-1 holding 10 of those. An Ankara IP address tells you which organization registered the block, not that a device using it sits in the city.
Internet exchanges in Ankara
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 |
|---|---|---|
RegPEX RegPEX - Regional Peering Exchange | 5 | 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 |
|---|---|---|
| Mars Datacenter Ankara-1 | 10 | Maliköy Anadolu OSB Mah. 29. Ekim Cad. No:8 Sincan |
| VAULTR ANKARA DATACENTER | 6 | Konya Yolu 30.Km Fetih Cd. Ogulbey Mh. No:4 A Blok |
| 3C1B HUAWEI FUSION DC ANKARA | 5 | ODTU Teknokent Universiteler Mahallesi |
| 3C1B TELEKOM TEPEPRIME | 3 | Tepe Prime Is Merkezi B Blok Garaj Katı Dumlupinar Bulvari No: 266 |
| Teknotel - Ankara | 1 | Konya Yolu 30.Km Fetih Cad. Oğulbey Mahallesi No:4 A Blok Gölbaşı |
| KERNZEN DC ANK-01 | 0 | Çamlıca Mah. Bağdat Cad. Yenimahalle / Ankara No:83 |
| Vodafone Pursaklar MTX | 0 | Vodafone TELEKOMUNIKASYON A S Emek cad.Polat sok. No:1 Pursaklar |
What a Ankara IP address tells you
RegPEX is the only exchange PeeringDB records in Ankara, and its 5 participants account for every exchange participation in the city. Interconnection here sits in colocation rather than on a fabric, and the numbers stay small either way, with 25 network presences spread across seven facilities. Mars Datacenter Ankara-1 holds 10 of them, VAULTR ANKARA DATACENTER 6, and 3C1B HUAWEI FUSION DC ANKARA 5, while KERNZEN DC ANK-01 and Vodafone Pursaklar MTX have no networks recorded. RegPEX publishes no mobile carrier ASN among its participants.
An address that resolves to Ankara in a geolocation database can be announced from anywhere its operator runs equipment. The city name comes from the registry record attached to the block, and that record carries one postal address for an organization that may route traffic through sites elsewhere in the country. Mobile blocks behave the same way at a wider scale, because a national operator hands out addresses from a shared pool and the subscribers behind one gateway all read as the same place.
With 5 exchange participants on record, the routing picture for an Ankara address comes from the prefix rather than from the city. The origin ASN naming the announcing operator, and the netname on the specific range, say more than the city string a lookup returns. A block registered to a national operator can read as Ankara while carrying traffic from anywhere that operator reaches, so treat the label as the operator's own paperwork.
Questions
Which internet exchanges are in Ankara?
PeeringDB records a single exchange in Ankara, RegPEX, listed as the Regional Peering Exchange, with 5 participants. The rest of the city's interconnection is in colocation, where seven facilities hold 25 network presences, and Mars Datacenter Ankara-1 is the busiest of them at 10.
Do Turkish mobile carriers peer in Ankara?
The data does not show it. RegPEX publishes no mobile carrier ASN on its participant list, and the carrier registry supplies no mobile ASNs for Turkey, so the record neither confirms nor denies mobile peering here. A facility named Vodafone Pursaklar MTX appears in the city with no networks recorded.
Does an Ankara IP address mean the user is in Ankara?
No. Geolocation databases read the location an operator publishes for an address block, and one record can cover a range used across the country. Mobile addresses sit behind gateways serving wide areas, so an Ankara result describes the block's registration more reliably than the device.
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