LINKINTEL: PeeringDB fix list

AS47655 · peeringdb.com/net/17082

PeeringDB

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

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

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

    3 connections, so 3 entries:

    IPv4178.18.226.210
    IPv62a03:5f80:4::226:210
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4178.18.224.19
    IPv62a03:5f80:4::224:19
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4178.18.226.127
    IPv62a03:5f80:4::226:127
    Speed20000 Mbps (20G)
    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.208.83
    IPv62001:7f8:20:101::208:83
    SpeedNot published
    RS peerYes
    IPv4195.208.210.144
    IPv62001:7f8:20:101::210:144
    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/47655/: 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.