ixreport

JSC MSK-IX: PeeringDB fix list

AS205022

2 things to fix in JSC MSK-IX's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

AS205022 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 JSC MSK-IX's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Kazan Kazan, Russia · PeeringDB 398From its IX-F export
    IPv4194.190.119.101
    IPv62001:7f8:20:801::119:101
    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.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.209.101
    IPv62001:7f8:20:101::209:101
    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/205022/: 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.