ixreport

M3.NET Transit: PeeringDB fix list

AS51465 · peeringdb.com/net/34004

PeeringDB

3 things to fix in M3.NET Transit's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on M3.NET Transit'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 differs10G100G
    • In the entry with IPv4 80.81.192.60: set Speed to 100000 (100G) (now 10000).
  2. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs20G5G
    • In the entry with IPv4 185.0.21.40: set Speed to 5000 (5G) (now 20000).
  3. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G30G
    • In the entry with IPv4 212.91.0.95: set Speed to 30000 (30G) (now 20000).
    • In the entry with IPv4 212.91.1.146: set Speed to 30000 (30G) (now 20000).
    • Add an entry: IPv4 212.91.0.95, IPv6 –, speed 30000 (30G).
    • Add an entry: IPv4 212.91.1.146, IPv6 –, speed 30000 (30G).

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