ixreport

Saint-Petersburg Computer Networks

AS44923 · AirNet

Saint-Petersburg Computer Networks Ltd.

7Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
7Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Saint-Petersburg Computer Networks? · Where should Saint-Petersburg Computer Networks peer next? · Compare Saint-Petersburg Computer Networks with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Saint-Petersburg Computer Networks's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Saint-Petersburg Computer Networks's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.226.212 178.18.226.214178.18.224.139 178.18.224.156 178.18.226.212 178.18.226.214
    IPv6 address missing from PeeringDB2a03:5f80:4::224:139 2a03:5f80:4::224:1562a03:5f80:4::224:139 2a03:5f80:4::224:156 2a03:5f80:4::226:212 2a03:5f80:4::226:214
    Port speed differs2 × 40G40G + 10G
    • In the entry with IPv4 178.18.226.212: set IPv6 to 2a03:5f80:4::226:212 (now 2a03:5f80:4::224:156).
    • In the entry with IPv4 178.18.226.214: set IPv6 to 2a03:5f80:4::226:214 (now 2a03:5f80:4::224:139).
    • Add an entry: IPv4 178.18.224.139, IPv6 2a03:5f80:4::224:139, speed 10000 (10G), RS peer yes.
    • Add an entry: IPv4 178.18.224.156, IPv6 2a03:5f80:4::224:156, speed 10000 (10G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Exchanges over time

02468Oct 3, 2026Nov 19, 20267
Show as a table
DateExchanges
Nov 19, 20267
Nov 18, 20267
Nov 17, 20267
Nov 16, 20267
Nov 15, 20267
Nov 14, 20267
Nov 13, 20267
Nov 12, 20267
Nov 11, 20267
Nov 10, 20267
Nov 9, 20267
Nov 8, 20267
Nov 7, 20267
Nov 6, 20267
Nov 5, 20267
Nov 4, 20267
Nov 3, 20267
Nov 2, 20267
Nov 1, 20267
Oct 31, 20267
Oct 30, 20267
Oct 29, 20267
Oct 28, 20267
Oct 27, 20267
Oct 26, 20267
Oct 25, 20267
Oct 24, 20267
Oct 23, 20267
Oct 22, 20267
Oct 21, 20267
Oct 20, 20267
Oct 19, 20267
Oct 18, 20267
Oct 17, 20267
Oct 16, 20267
Oct 15, 20267
Oct 14, 20267
Oct 13, 20267
Oct 12, 20267
Oct 11, 20267
Oct 10, 20267
Oct 9, 20267
Oct 8, 20267
Oct 7, 20267
Oct 6, 20267
Oct 5, 20267
Oct 4, 20267
Oct 3, 20267

Map

Where Saint-Petersburg Computer Networks's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 360G across 7 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.212
178.18.226.214
2a03:5f80:4::224:139
2a03:5f80:4::224:156
2 × 40G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.146 40G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.114 40G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.155 40G Yes PeeringDB
Russia PITER-IX Rostov Rostov, Russia 193.27.38.41 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.29
185.1.153.249
2 × 40G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.179 40G Yes PeeringDB

Exchanges in its buildings that it isn't on (5)

These exchanges have a switch in a facility where Saint-Petersburg Computer Networks lists itself in PeeringDB, but don't have Saint-Petersburg Computer Networks as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands Global-IXAmsterdam, Netherlands 138 Raduga-2
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Raduga-2
Russia CLOUD-IX MSKMoscow, Russia 52 Raduga-2
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Raduga-2
Russia PIRIXSt.Petersburg, Russia 6 Raduga-2
Facilities (2)

The buildings Saint-Petersburg Computer Networks lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Raduga-2St. Petersburg 3 of 8
Russia COD BM-18St.Petersburg No exchange

Recent changes Search them

  • Oct 22, 2026 [PDB] AS44923 Saint-Petersburg Computer Networks now in PeeringDB at GNM-IX