Ekaterinburg · Russia
PeeringDB records two exchanges in Ekaterinburg. MSK-IX Ekaterinburg has 33 participants and CLOUD-IX EKT six, for 39 in total, while six facilities report 48 network presences, 17 of them at Erlang.Ekb.MS145 and 17 at EKB, Uralcod. An address geolocating to Ekaterinburg shows an operator's registration rather than a device in the city.
Internet exchanges in Ekaterinburg
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 |
|---|---|---|
MSK-IX Ekaterinburg MSK-IX Ekaterinburg (former EKT-IX) | 33 | none in the registry |
CLOUD-IX EKT | 6 | 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 |
|---|---|---|
| EKB, Uralcod | 17 | Sheinkmana 10 |
| Erlang.Ekb.MS145 | 17 | Ulitsa Mamina-Sibiryaka 145 Oktyabr'skiy Rayon |
| DataHouse Ekaterinburg | 5 | Sibirskiy trakt, 8B |
| Erlang.Ekb.SH10 | 5 | Ulitsa Sheynkmana 10 Verkh-Isetskiy Rayon |
| Ekaterinburg ABV | 2 | Radischeva 60A |
| KeyPoint Ekateriburg | 2 | Парк CRAFT Кольцевая автодорога 17 километр, 1 |
What a Ekaterinburg IP address tells you
Ekaterinburg's recorded peering runs through two exchanges. MSK-IX Ekaterinburg holds 33 of the city's 39 participant records and CLOUD-IX EKT the other six. Colocation is on a similar scale, with six facilities reporting 48 networks between them. Erlang.Ekb.MS145 and EKB, Uralcod account for 17 each, DataHouse Ekaterinburg and Erlang.Ekb.SH10 for five each, and Ekaterinburg ABV and KeyPoint Ekateriburg for two each. The registry attaches no carrier ASN to either exchange, so it documents no Russian mobile operator peering in the city.
An address that geolocates to Ekaterinburg can belong to a connection anywhere the announcing network reaches. Operators register a block once and put a single location on the record, then route it as their network requires. Mobile subscribers pass through a small number of gateways, so a session that starts in another region leaves through addresses registered elsewhere. Geolocation databases copy the location the operator published, which is why the same city shows up in every lookup even when the user is nowhere near it.
The origin ASN on the prefix and the netname registered against it tell you more than a city name. The ASN names the network that announced the range and the netname carries whatever label its owner filed, which sometimes marks a mobile pool or a regional allocation. Neither connects the address to MSK-IX Ekaterinburg or to any of the six facilities, since 39 participant records describe where networks meet in the city and say nothing about which customer holds a given address.
Questions
Which internet exchanges are in Ekaterinburg?
Two. MSK-IX Ekaterinburg, listed with 33 participants, and CLOUD-IX EKT with six, giving 39 participant records for the city. Networks that peer privately inside one of the six facilities are not counted in those figures.
Do Russian mobile carriers peer in Ekaterinburg?
Not in the registry. It attaches no carrier ASN to MSK-IX Ekaterinburg or CLOUD-IX EKT, so no mobile operator appears as a participant. An operator can carry traffic through the city's facilities without entering that presence in PeeringDB, so the absence is a gap in the record.
Does an IP that geolocates to Ekaterinburg mean the device is there?
No. The label comes from the registration on the address block and the location the operator published for it. A subscriber elsewhere in Russia can leave through a gateway with Ekaterinburg addresses, and databases reading that registration will place the session in the 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