Saint-Petersburg Computer Networks: PeeringDB fix list

AS44923 · peeringdb.com/net/19233

PeeringDB

One thing to fix in Saint-Petersburg Computer Networks's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 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.

Add these exchanges (1)

On the exchange's own member list, but not in Saint-Petersburg Computer Networks's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.226.212
    IPv62a03:5f80:4::226:212
    Speed40000 Mbps (40G)
    RS peerYes
    IPv4178.18.226.214
    IPv62a03:5f80:4::226:214
    Speed40000 Mbps (40G)
    RS peerYes

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

From ixreport.com/net/44923/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.