ixreport

vdsina: PeeringDB fix list

AS48282

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

AS48282 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 vdsina'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.227.76
    IPv62a03:5f80:4::227:76
    Speed800000 Mbps (800G)
    RS peerYes
    IPv4178.18.227.77
    IPv62a03:5f80:4::227:77
    Speed800000 Mbps (800G)
    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 Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.209.164
    IPv62001:7f8:20:101::209:164
    SpeedNot published
    RS peerYes
    IPv4195.208.210.31
    IPv62001:7f8:20:101::210:31
    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/48282/: 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.