ixreport

Perceval: PeeringDB fix list

AS5463 · peeringdb.com/net/27570

PeeringDB

2 things to fix in Perceval's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Perceval'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 (2)

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. Belgium BNIX Brussels, Belgium · PeeringDB 59
    ProblemPeeringDB hasThe export has
    Port speed differs2.048G2G
    • In the entry with IPv4 194.53.172.80: set Speed to 2000 (2G) (now 2048).

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

  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs1.024G5G
    • In the entry with IPv4 5.57.82.44: set Speed to 5000 (5G) (now 1024).

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