ixreport

PP "New information systems": PeeringDB fix list

AS41820 · peeringdb.com/net/10468

2 things to fix in PP "New information systems"'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 12:40 UTC.

Make the changes on PP "New information systems"'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs20G400G
    • In the entry with IPv4 80.81.196.93: set Speed to 400000 (400G) (now 20000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If PP "New information systems" has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958Not on its website members list
    IPv4185.0.43.131
    IPv62001:7f8:115:1::1:131
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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