Moscow · Russia
PeeringDB records ten internet exchanges in Moscow, and MSK-IX Moscow has the most participants at 305, ahead of PITER-IX Moscow at 238. Forty-seven facilities hold 635 network presences, 275 of them at Moscow M9. An address geolocating to Moscow reflects where an operator registered the block, not where a device sits.
Internet exchanges in Moscow
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 Moscow | 305 | none in the registry |
PITER-IX Moscow | 238 | |
Eurasia Peering IX Eurasia Peering LLC | 137 | none in the registry |
W-IX | 66 | none in the registry |
CLOUD-IX MSK | 53 | none in the registry |
MegaFon-IX | 12 | none in the registry |
BGP.Exchange - Moscow | 12 | none in the registry |
Linxdatacenter-IX Linxdatacenter Internet Exchange | 5 | none in the registry |
DataLine-IX | 4 | none in the registry |
SPACE-IX | 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 |
|---|---|---|
| Moscow M9 | 275 | 7, Butlerova street |
| IXcellerate MOS1 | 39 | Altufievskoe shosse 33G |
| Moscow M10 | 37 | Suschevskiy val 26 |
| Moscow TehnoGorod | 36 | 40 bld.1 3rd Maryna Roshha driveway |
| DataLine Moscow DC OST | 31 | Moscow, ul. Borovaya, 7, bldg. 10 |
| Linxdatacenter (Moscow) | 25 | 8 Marta 14 |
| DataLine Moscow DC NORD | 25 | Moscow, Korovinskoye shosse, 41 |
| DataSpace Moscow | 19 | Sharikopodshipnikovskaya st.11, Bldg. 8 |
| StoreData | 16 | Nizhegorodskaya st., 32 |
| Stack.M1 | 14 | 125, Varshavskoe road Bldg. 1 |
| DataPro Moscow | 14 | 69 Aviamotornaya str. |
| DataHouse Moscow | 12 | Elektrolitnyy Proyezd, 3, stroenie 1 |
Showing the 12 facilities with the most networks, of 47 recorded.
What a Moscow IP address tells you
Ten exchanges appear under Moscow in PeeringDB and together they account for 832 participant records. MSK-IX Moscow carries 305 of them and PITER-IX Moscow 238, with Eurasia Peering IX at 137 and W-IX at 66 behind those two, and the remaining six range from 53 down to none at SPACE-IX. Colocation carries comparable weight, with 47 facilities reporting 635 network presences and Moscow M9 holding 275 of those on its own. PITER-IX Moscow is the only exchange the registry marks with a mobile carrier ASN, AS13194.
An address that a database places in Moscow often belongs to a block announced from a registry record rather than to a machine inside the city. Operators register an allocation once, give it a single address, and announce it wherever the routing suits them. Mobile traffic compounds this because subscriber sessions leave through a small number of gateways, and those gateways need not be anywhere near the handset. Geolocation databases read the operator's published location and repeat it, so a connection from far outside the city can still resolve here.
Someone checking an address gets more from the origin ASN and the netname on the specific prefix than from the city field. The ASN says which network announced the block, and the netname often carries the operator's own label for the customer or region it assigned. Neither confirms that the traffic passed through MSK-IX Moscow, Moscow M9 or any of the other 46 facilities on record. PeeringDB describes where networks meet and a routing record describes who announces an address, so the two answer different questions.
Questions
Which internet exchanges are in Moscow?
PeeringDB lists ten. MSK-IX Moscow has the most participants at 305, followed by PITER-IX Moscow at 238, Eurasia Peering IX at 137, W-IX at 66 and CLOUD-IX MSK at 53. MegaFon-IX, BGP.Exchange - Moscow, Linxdatacenter-IX, DataLine-IX and SPACE-IX each report 12 or fewer.
Do Russian mobile carriers peer in Moscow?
The registry records one carrier ASN, AS13194, at PITER-IX Moscow. The other nine exchanges in the city carry no carrier ASN, which reflects what operators chose to publish about themselves rather than proof that no other mobile network exchanges traffic in Moscow.
Does an IP that geolocates to Moscow mean the device is there?
No. The city label comes from the registration on the address block and from the operator's published location. A subscriber connecting from elsewhere in Russia can leave through a gateway whose addresses carry a Moscow registration, and every database copying that record places 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