Objedinennye Seti: PeeringDB fix list
AS198539 · peeringdb.com/net/27539
One thing to fix in Objedinennye Seti's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Objedinennye 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 IPv6 address in PeeringDB, not in the export 2001:7f8:20:101::210:126 2001:7f8:20:101::210:160 2001:7f8:20:101::210:126 - In the entry with IPv4 195.208.210.160: set IPv6 to (empty) (now 2001:7f8:20:101::210:160).
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/198539/: 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.