Leon: PeeringDB fix list

AS13000 · peeringdb.com/net/9311

PeeringDB

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

Make the changes on Leon'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 80.81.195.93: set Speed to 100000 (100G) (now 30000).
  2. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 40G100G + 40G
    • In the entry with IPv4 178.216.40.23: set Speed to 100000 (100G) (now 40000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G10G
    • In the entry with IPv4 212.91.0.219: set Speed to 10000 (10G) (now 20000).
    • In the entry with IPv4 212.91.0.222: set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 212.91.0.219, IPv6 –, speed 10000 (10G).
    • Add an entry: IPv4 212.91.0.222, IPv6 –, speed 10000 (10G).

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