fastvps.ru: PeeringDB fix list

AS200487

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

AS200487 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

On the exchange's own member list, but not in fastvps.ru'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.224.184
    IPv62a03:5f80:4::224:184
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.226.106
    IPv62a03:5f80:4::226:106
    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

    4 connections, so 4 entries:

    IPv4194.226.102.54
    IPv62001:7f8:20:202::102:54
    SpeedNot published
    RS peerYes
    IPv4194.226.101.54
    IPv62001:7f8:20:201::101:54
    SpeedNot published
    RS peerYes
    IPv4194.226.100.54
    IPv62001:7f8:20:201::100:54
    SpeedNot published
    RS peerYes
    IPv4194.226.103.54
    IPv62001:7f8:20:202::103:54
    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/200487/: 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.