ixreport

Ian Chilton: PeeringDB fix list

AS57483 · peeringdb.com/net/29490

PeeringDB

One thing to fix in Ian Chilton's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Ian Chilton'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. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB5.57.83.105.57.83.9 5.57.83.10
    IPv6 address missing from PeeringDB2001:7f8:17::e08b:12001:7f8:17::e08b:1 2001:7f8:17::e08b:2
    Port speed differs1G10G + 2G
    • In the entry with IPv4 5.57.83.10: set Speed to 10000 (10G) (now 1000).
    • Add an entry: IPv4 5.57.83.9, IPv6 2001:7f8:17::e08b:2, speed 2000 (2G), RS peer yes.

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