ixreport

Компьютерная информационная технология: PeeringDB fix list

AS48257 · peeringdb.com/net/10529

PeeringDB

One thing to fix in Компьютерная информационная технология's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Компьютерная информационная технология'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.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.224.133178.18.224.133 178.18.225.174
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:133 2a03:5f80:4::225:174
    • In the entry with IPv4 178.18.224.133: set IPv6 to 2a03:5f80:4::224:133 (now empty).
    • Add an entry: IPv4 178.18.225.174, IPv6 2a03:5f80:4::225:174, 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.

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