Nizhnetagilskie Kompyuternye Seti: PeeringDB fix list
AS49218 · peeringdb.com/net/11970
2 things to fix in Nizhnetagilskie Kompyuternye Seti's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Nizhnetagilskie Kompyuternye Seti'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 178.18.233.8 178.18.224.156 178.18.225.221 178.18.233.8 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:156 2a03:5f80:4::225:221 2a03:5f80:4:1::233:8 Port speed differs 20G 20G + 10G - In the entry with IPv4 178.18.233.8: set IPv6 to 2a03:5f80:4:1::233:8 (now empty); set Speed to 10000 (10G) (now 20000).
- Add an entry: IPv4 178.18.224.156, IPv6 2a03:5f80:4::224:156, speed 10000 (10G), RS peer yes.
- Add an entry: IPv4 178.18.225.221, IPv6 2a03:5f80:4::225:221, speed 20000 (20G), 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 Nizhnetagilskie Kompyuternye Seti 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.44 IPv6 – Speed 20000 Mbps (20G)
From ixreport.com/net/49218/: 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.