ixreport

Vimpel-Communication: PeeringDB fix list

AS31359

One thing to fix in Vimpel-Communication's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 21:56 UTC.

AS31359 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 Vimpel-Communication's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export
    IPv4194.85.107.60
    IPv6–
    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/31359/: 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.