ixreport

T2 Russia Network: PeeringDB fix list

AS12958 · peeringdb.com/net/1796

PeeringDB

One thing to fix in T2 Russia Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on T2 Russia Network'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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:20 2a03:5f80:4::226:31 2a03:5f80:4::226:38
    Port speed differs3 × 300G700G + 2 × 300G
    • In the entry with IPv4 178.18.226.20: set IPv6 to 2a03:5f80:4::226:20 (now empty).
    • In the entry with IPv4 178.18.226.31: set IPv6 to 2a03:5f80:4::226:31 (now empty).
    • In the entry with IPv4 178.18.226.38: set IPv6 to 2a03:5f80:4::226:38 (now empty); set Speed to 700000 (700G) (now 300000).

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