ixreport

SkyNet SPB: PeeringDB fix list

AS35807 · peeringdb.com/net/21059

PeeringDB

2 things to fix in SkyNet SPB's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.

Make the changes on SkyNet SPB'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 SkyNet SPB'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.225.73
    IPv62a03:5f80:4::225:73
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.24
    IPv62a03:5f80:4::226:24
    Speed100000 Mbps (100G)
    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

    4 connections, so 4 entries:

    IPv4194.226.102.59
    IPv62001:7f8:20:202::102:59
    SpeedNot published
    RS peerYes
    IPv4194.226.100.59
    IPv62001:7f8:20:201::100:59
    SpeedNot published
    RS peerYes
    IPv4194.226.100.63
    IPv62001:7f8:20:201::100:63
    SpeedNot published
    RS peerYes
    IPv4194.226.102.63
    IPv62001:7f8:20:202::102:63
    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/35807/: 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.