Kyiv · Ukraine
PeeringDB files two exchanges under Kyiv, BGP.Exchange - Kyiv with 11 participants and IXP Liptel with none recorded, plus 34 colocation facilities holding 534 networks. NewTelco Kiev reports 165 of them. Almost all documented capacity here sits in buildings rather than at an exchange, so a Kyiv address reflects an operator's registration rather than a device.
Internet exchanges in Kyiv
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 |
|---|---|---|
BGP.Exchange - Kyiv | 11 | none in the registry |
IXP Liptel | 0 | 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 |
|---|---|---|
| NewTelco Kiev | 165 | Gaidara 50 |
| Ucomline Kiev | 75 | Leontovicha 9 Building 3 |
| 9 Leontovicha | 45 | 9 Leontovicha Street Building 2 |
| Giganet | 32 | Nowhere street, 9 |
| BeMobile | 26 | Kurenivska St, 21-A |
| TSUA | 24 | Leontovicha 9, building 3, flour 3 |
| Data Center Ukr-Com | 19 | 50b Simyi Prakhovykh Str. |
| Omega Telecom Kyiv | 17 | Vatslava Havela Blvd., 4 |
| TOPNET/UA/Leontovicha9 | 15 | 9 Leontovicha Street |
| Data Center G50 | 15 | 50 B, Gaidara str. |
| Datagroup Kiev | 13 | str. Simyi Brodskykh, 31/33 |
| KievNet/L9 | 13 | 9, Leontovicha str. |
Showing the 12 facilities with the most networks, of 34 recorded.
What a Kyiv IP address tells you
BGP.Exchange - Kyiv is the better connected of the two exchanges on record, with 11 participants, while IXP Liptel carries no participant count at all. Colocation holds far more, 534 networks across 34 facilities, with NewTelco Kiev on 165, Ucomline Kiev on 75, 9 Leontovicha on 45 and Giganet on 32. Neither exchange has a carrier ASN attached, so none of Ukraine's three mobile operators, Kyivstar on AS15895, lifecell on AS34058 and Vodafone Ukraine on AS21497, shows as peering under this spelling of the city name.
An address that a database places in Kyiv need not be a device in Kyiv. Operators announce address blocks from a registry record that carries one location for an entire allocation, and mobile traffic leaves a network through a small number of gateways that can sit a long way from the subscriber. Geolocation providers read the operator's own published location and repeat it, so a connection from anywhere in Ukraine can resolve to Kyiv in a lookup while the handset never came near any of the 34 facilities on record.
Someone checking an address gets more from the origin ASN and the netname on the specific prefix than from the city field. The ASN names the network that announced the block, and the netname shows how that network chose to describe the range, including whether it is set aside for mobile subscribers. Neither says the traffic crossed BGP.Exchange - Kyiv or entered one of the listed buildings. The 11 participants and 534 facility networks describe where peering is documented in Kyiv, not where a given address sits.
Mobile carriers in Ukraine
A mobile address in Kyiv is routed by one of the country's operators. Each entry lists the operator's ASNs, so you can check which network an address belongs to.
Questions
Which internet exchanges are in Kyiv?
PeeringDB lists two under this spelling, BGP.Exchange - Kyiv with 11 participants and IXP Liptel with no participant count recorded. Networks that peer privately inside one of the 34 colocation facilities, rather than across an exchange fabric, do not appear in either figure.
Do Ukraine mobile carriers peer in Kyiv?
Neither exchange filed under Kyiv has a carrier ASN attached, so Kyivstar, lifecell and Vodafone Ukraine show no peering presence in this record. That is silence in the registry rather than proof that the three operators exchange no traffic in the city.
Does an IP that geolocates to Kyiv mean the device is there?
No. The city label comes from the address block's registration and the operator's published location, not from the device. A subscriber elsewhere in Ukraine can leave through a gateway whose addresses are registered in Kyiv and will read as Kyiv in any database copying that record.
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