Intersvyaz: PeeringDB fix list

AS8369 · peeringdb.com/net/17927

PeeringDB

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

Make the changes on Intersvyaz'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 Intersvyaz's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    6 connections, so 6 entries:

    IPv4178.18.224.180
    IPv62a03:5f80:4::224:180
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.43
    IPv62a03:5f80:4::225:43
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.158
    IPv62a03:5f80:4::226:158
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.62
    IPv62a03:5f80:4::226:62
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.92
    IPv62a03:5f80:4::226:92
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.95
    IPv62a03:5f80:4::226:95
    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 Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export

    2 connections, so 2 entries:

    IPv4194.85.107.78
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4194.85.107.67
    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.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.26 195.208.208.228195.208.208.26 195.208.208.228 195.208.210.124 195.208.210.138
    • Add an entry: IPv4 195.208.210.138, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.210.124, IPv6 –, RS peer yes.

    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/8369/: 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.