ixreport

Runet Business Systems: PeeringDB fix list

AS60544 · peeringdb.com/net/26505

PeeringDB

2 things to fix in Runet Business Systems's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

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

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs200M200G
    • In the entry with IPv4 80.81.192.145: set Speed to 200000 (200G) (now 200).
  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:20:101::208:197 2001:7f8:20:101::210:662001:7f8:20:101::208:197
    • In the entry with IPv4 195.208.210.66: set IPv6 to (empty) (now 2001:7f8:20:101::210:66).

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