RELARN: PeeringDB fix list

AS3316 · peeringdb.com/net/17093

PeeringDB

One thing to fix in RELARN's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

Make the changes on RELARN'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 (1)

On the exchange's own member list, but not in RELARN's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    3 connections, so 3 entries:

    IPv4195.208.210.88
    IPv62001:7f8:20:101::210:88
    SpeedNot published
    RS peerYes
    IPv4195.208.210.2
    IPv62001:7f8:20:101::210:2
    SpeedNot published
    RS peerYes
    IPv4195.208.208.34
    IPv62001:7f8:20:101::208:34
    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/3316/: 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.