EvolveIP AS59439: PeeringDB fix list

AS59439 · peeringdb.com/net/6640

PeeringDB

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

Make the changes on EvolveIP AS59439'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::e82f:1
    • In the entry with IPv4 195.66.224.229: set IPv6 to 2001:7f8:4::e82f:1 (now empty).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:17::e82f:1
    • In the entry with IPv4 5.57.81.190: set IPv6 to 2001:7f8:17::e82f:1 (now empty).

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