MSK-IX Vladivostok: operator report

Vladivostok, Russia · PeeringDB 378 · ixreport.com/ix/378/report/

Download CSV

Members of MSK-IX Vladivostok that PeeringDB has wrong, from its IX-F export (13 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 7 networks to follow up; 1 with a public PeeringDB contact.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (5)

These networks could add MSK-IX Vladivostok to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS12389 Rostelecom PeeringDBIX-F 193.232.136.46
2001:7f8:20:701::136:46
No public contact
AS34470 PortTelekomIX-F 193.232.136.35 No PeeringDB record
AS42038 Vladivostokskaya Set Ltd PeeringDBIX-F 193.232.136.39 No public contact
AS48531 MSK-IX Vladivostok Route ServersIX-F 193.232.136.100
193.232.136.200
2001:7f8:20:701::136:100
2001:7f8:20:701::136:200
No PeeringDB record
AS201512 WildberriesIX-F 193.232.136.34 No PeeringDB record

Addresses or port speeds that differ (0)

PeeringDB against your IX-F export, for the 8 networks in both. Either the network's PeeringDB record or the export is out of date.

None: every network's addresses and port speed match.

In PeeringDB, not on your lists (2)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

NetworkIn PeeringDBContact
AS25091 IP-Max SA PeeringDB 193.232.136.93
2001:7f8:20:701::136:93
1G
Technical: email address (needs JavaScript)
AS57463 NetIX Communications PeeringDB 193.232.136.38
2001:7f8:20:701::136:38
No public contact