Novaya Sibir Plus: PeeringDB fix list
AS42574 · peeringdb.com/net/13867
2 things to fix in Novaya Sibir Plus's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 21:56 UTC.
Make the changes on Novaya Sibir Plus's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.232.87.60 193.232.87.60 193.232.87.82 - Add an entry: IPv4 193.232.87.82, IPv6 –, 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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Novaya Sibir Plus has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.208.210.60 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/42574/: 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.