IXLeeds Route Collectors: PeeringDB fix list
AS51526 · peeringdb.com/net/24534
One thing to fix in IXLeeds Route Collectors's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on IXLeeds Route Collectors'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.
-
Problem PeeringDB has The export has IPv4 address differs 91.217.231.1 91.217.231.254 IPv6 address differs 2001:7f8:67::1 2001:7f8:67::c946:1 - In the entry with IPv4 91.217.231.1: set IPv4 to 91.217.231.254 (now 91.217.231.1); set IPv6 to 2001:7f8:67::c946:1 (now 2001:7f8:67::1).
From ixreport.com/net/51526/: 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.