ixreport

Connexin Limited: PeeringDB fix list

AS199775 · peeringdb.com/net/10497

PeeringDB

5 things to fix in Connexin Limited's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Connexin 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 (5)

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 IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:67::3:c5f:1
    • In the entry with IPv4 91.217.231.33: set IPv6 to 2001:7f8:67::3:c5f:1 (now empty).
  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:c5f:2
    • In the entry with IPv4 195.66.225.117: set IPv6 to 2001:7f8:4::3:c5f:2 (now empty).
  3. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1:0:3:c5f:1
    • In the entry with IPv4 195.66.237.117: set IPv6 to 2001:7f8:4:1:0:3:c5f:1 (now empty).
  4. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:2:0:3:c5f:1
    • In the entry with IPv4 195.66.244.16: set IPv6 to 2001:7f8:4:2:0:3:c5f:1 (now empty).
  5. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:17::3:c5f:1
    • In the entry with IPv4 5.57.82.130: set IPv6 to 2001:7f8:17::3:c5f: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/199775/: 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.