ixreport

VimpelCom: PeeringDB fix list

AS3216 · peeringdb.com/net/1265

PeeringDB

3 things to fix in VimpelCom's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on VimpelCom'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 (2)

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

  1. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.151
    IPv62001:7f8:d:fb::151
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.151
    IPv62001:7f8:d:fc::151
    SpeedNot published
    RS peerYes

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.95178.18.225.35 178.18.236.95
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:952a03:5f80:4::225:35 2a03:5f80:4:2::236:95
    • Add an entry: IPv4 178.18.225.35, IPv6 2a03:5f80:4::225:35, speed 100000 (100G), RS peer yes.

    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/3216/: 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.