MSK-IX Ekaterinburg Route Servers: PeeringDB fix list

AS43213

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

AS43213 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 Ekaterinburg Route Servers's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export

    2 connections, so 2 entries:

    IPv4194.85.107.200
    IPv62001:7f8:20:301::107:200
    SpeedNot published
    RS peerYes
    IPv4194.85.107.100
    IPv62001:7f8:20:301::107: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/43213/: 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.