City network · Russia
St. Petersburg internet exchanges, data centers and carriers
PeeringDB's 2026-09-07 snapshot records 4 internet exchanges and 20 colocation facilities in St. Petersburg, Russia. The largest exchange is MSK-IX Saint-Petersburg, with 60 participant entries.
- Exchanges
- 4
- Facilities
- 20
- Snapshot
- 2026-09-07
- Country
- Russia (RU)
- Internet exchanges
- 4
- Largest exchange
- MSK-IX Saint-Petersburg (60 participants)
- Exchange participant entries
- 93
- Colocation facilities
- 20
- Facility network presences
- 318
- Registry carriers peering here
- none recorded
- Snapshot
- 2026-09-07
The 2026-09-07 PeeringDB snapshot records 4 exchanges and 20 facilities in St. Petersburg, Russia. Their entries sum to 93 exchange participants and 318 facility network presences; the same network can appear more than once.
Internet exchanges in St. Petersburg
| Exchange | Participants | Registry carriers peering |
|---|---|---|
| MSK-IX Saint-PetersburgMSK-IX Saint-Petersburg (former SPB-IX) | 60 | none in the registry |
| CLOUD-IX SPB | 25 | none in the registry |
| PIRIXPirix Internet Exchange | 6 | none in the registry |
| CODIX | 2 | none in the registry |
Colocation facilities in St. Petersburg
| Facility | Networks present | Address |
|---|---|---|
| Bolshaya Morskaya 18 | 62 | ul. Bolshaya Morskaya, 18 |
| Raduga-2 | 58 | 12 Kantemirovskaya str |
| Tsvetochnaya Data Center | 47 | Tsvetochnaya 19+21 |
| IVC ORW Saint-Petersburg | 39 | Borovaya 57 |
| RETNNet OV DC | 27 | 61A, Obvodnyy kanal |
| Miran-2 | 17 | Евпаторийский пер. 7А |
| Data-Center IMAQLIQ | 16 | Sedova 11B |
| Linxdatacenter (Saint-Petersburg) | 13 | Repishcheva ulitsa 20a |
| Xelent | 12 | Vyborgskoe highway 503/12 |
| COD BM-18 | 9 | Bolshaya Morskaya 18 |
| BONCH-IT | 7 | embankment river Moyka, 61 |
| DataHouse Saint Petersburg | 4 | Stepana Razina 8AG |
Showing the 12 facilities with the most networks, of 20 recorded.
What these records establish
This page groups the saved exchange and facility records for St. Petersburg. A sum of participant or facility counts is not a count of unique networks, traffic volume, available capacity or service coverage.
PeeringDB is user-maintained. Its records describe reported interconnection infrastructure; they do not trace a particular request or locate a subscriber. A missing record in this snapshot is not proof that an operator has no presence or private connection in the area.
An IP geolocation result is a separate estimate. MaxMind documents accuracy limits and explains that its location data cannot identify a specific household, person or street address. This registry does not perform a geolocation lookup or measure where an individual device is located.
Questions
- How many exchanges and facilities are recorded in St. Petersburg?
- 4 exchanges and 20 facilities appear in the 2026-09-07 snapshot. The tables show the saved records and link to the publisher for current details.
- Are the totals unique networks?
- No. Participant entries are summed across exchanges and network presences across facilities. A network listed at several locations contributes to several entries.
- Does a St. Petersburg IP label prove that a device is there?
- No. These infrastructure records do not establish a device location. Consult the geolocation provider’s accuracy information and the specific network record for the claim you are evaluating.
Sources
PeeringDB supplies the exchanges, participant counts, facilities and network presence (snapshot 2026-09-07); MaxMind documents the limits of IP geolocation; the PROXIES.SX carrier registry supplies the operator ASNs used to match peering participants.
These records describe where networks interconnect. A St. Petersburg IP address does not show that a device is in St. Petersburg: mobile carriers route traffic from wide areas through shared gateways, and geolocation databases estimate from registration data.