MSK-IX Rostov-on-Don Route Servers: PeeringDB fix list

AS48216

One thing to fix in MSK-IX Rostov-on-Don Route Servers's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

AS48216 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (1)

On the exchange's own member list, but not in MSK-IX Rostov-on-Don Route Servers's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380From its IX-F export

    2 connections, so 2 entries:

    IPv4193.232.140.200
    IPv62001:7f8:20:501::140:200
    SpeedNot published
    RS peerYes
    IPv4193.232.140.100
    IPv62001:7f8:20:501::140:100
    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/48216/: 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.