Pure IP: PeeringDB fix list

AS204264 · peeringdb.com/net/9570

PeeringDB

2 things to fix in Pure IP's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Pure IP'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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:1de8:1
    Port speed differs1.024G10G
    • In the entry with IPv4 195.66.226.219: set IPv6 to 2001:7f8:4::3:1de8:1 (now empty); set Speed to 10000 (10G) (now 1024).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1:0:3:1de8:1
    Port speed differs100M1G
    • In the entry with IPv4 195.66.238.219: set IPv6 to 2001:7f8:4:1:0:3:1de8:1 (now empty); set Speed to 1000 (1G) (now 100).

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