WEBDISCOUNT: PeeringDB fix list

AS24637 · peeringdb.com/net/13209

PeeringDB

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

Make the changes on WEBDISCOUNT's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in WEBDISCOUNT's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.227.44
    IPv62001:7f8:4::603d:1
    Speed10000 Mbps (10G)
    RS peerNo
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list
    IPv4195.66.239.44
    IPv62001:7f8:4:1::603d:1
    Speed10000 Mbps (10G)
    RS peerNo

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.

  1. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:b:100:1d1:a5d2:4637:105none
    Port speed differs100M1G
    • In the entry with IPv4 217.29.66.105: set IPv6 to (empty) (now 2001:7f8:b:100:1d1:a5d2:4637:105); set Speed to 1000 (1G) (now 100).

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