ixreport

Wessex Internet: PeeringDB fix list

AS206347 · peeringdb.com/net/14684

PeeringDB

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

Make the changes on Wessex Internet'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
    IPv4 address missing from PeeringDB195.66.227.108195.66.227.108 195.66.231.124
    IPv6 address missing from PeeringDB2001:7f8:4::3:260b:12001:7f8:4::3:260b:1 2001:7f8:4::3:260b:2
    Port speed differs10G2 × 100G
    • In the entry with IPv4 195.66.227.108: set Speed to 100000 (100G) (now 10000).
    • Add an entry: IPv4 195.66.231.124, IPv6 2001:7f8:4::3:260b:2, speed 100000 (100G), RS peer yes.
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 195.66.239.108: set Speed to 10000 (10G) (now 1000).

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