ValueHOST: PeeringDB fix list

AS40966 · peeringdb.com/net/7756

PeeringDB

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

Make the changes on ValueHOST'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 (6)

On the exchange's own member list, but not in ValueHOST'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.202
    IPv62a03:5f80:4::225:202
    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 Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export
    IPv4194.85.107.48
    IPv6–
    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.

  3. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.210.136
    IPv6–
    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.

  4. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export
    IPv4193.232.87.91
    IPv6–
    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.

  5. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380From its IX-F export
    IPv4193.232.140.61
    IPv6–
    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.

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

    2 connections, so 2 entries:

    IPv4194.226.100.33
    IPv62001:7f8:20:201::100:33
    SpeedNot published
    RS peerYes
    IPv4194.226.102.33
    IPv62001:7f8:20:202::102:33
    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/40966/: 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.