IP River Limited: PeeringDB fix list
AS62163 · peeringdb.com/net/27877
2 things to fix in IP River Limited's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 21:35 UTC.
Make the changes on IP River Limited'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 IPv6 address differs 2001:7f8:4:1::3172:1 2001:7f8:4:1::f2d3:1 - In the entry with IPv4 195.66.237.154: set IPv6 to 2001:7f8:4:1::f2d3:1 (now 2001:7f8:4:1::3172:1).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If IP River Limited has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members listIPv4 195.66.244.72 IPv6 2001:7f8:4:2::f2d3:1 Speed 10000 Mbps (10G)
From ixreport.com/net/62163/: 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.