ixreport

CRELCOM: PeeringDB fix list

AS6789 · peeringdb.com/net/3757

PeeringDB

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

Make the changes on CRELCOM'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 (3)

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.226.196178.18.225.54 178.18.226.196
    IPv6 address missing from PeeringDB2a03:5f80:4::226:1962a03:5f80:4::225:54 2a03:5f80:4::226:196
    Port speed differs200G10G
    • In the entry with IPv4 178.18.226.196: set Speed to 10000 (10G) (now 200000).
    • Add an entry: IPv4 178.18.225.54, IPv6 2a03:5f80:4::225:54, speed 10000 (10G), 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.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.210.127195.208.209.29 195.208.210.127 195.208.210.161 195.208.210.164
    IPv6 address missing from PeeringDB2001:7f8:20:101::210:1272001:7f8:20:101::209:29 2001:7f8:20:101::210:127
    • Add an entry: IPv4 195.208.210.164, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.210.161, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.209.29, IPv6 2001:7f8:20:101::209:29, 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.

  3. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.232.140.49193.232.140.49 193.232.140.60
    IPv6 address missing from PeeringDBnone2001:7f8:20:501::140:49 2001:7f8:20:501::140:60
    • In the entry with IPv4 193.232.140.49: set IPv6 to 2001:7f8:20:501::140:49 (now empty).
    • Add an entry: IPv4 193.232.140.60, IPv6 2001:7f8:20:501::140:60, 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.

From ixreport.com/net/6789/: 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.