Petrosvyaz: PeeringDB fix list

AS50538 · peeringdb.com/net/26611

PeeringDB

2 things to fix in Petrosvyaz's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 20:58 UTC.

Make the changes on Petrosvyaz'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 (2)

On the exchange's own member list, but not in Petrosvyaz's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.225.154
    IPv62a03:5f80:4::225:154
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    2 connections, so 2 entries:

    IPv4194.226.100.49
    IPv62001:7f8:20:201::100:49
    SpeedNot published
    RS peerYes
    IPv4194.226.102.49
    IPv62001:7f8:20:202::102:49
    SpeedNot published
    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/50538/: 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.