Telecom Plus: PeeringDB fix list

AS51553 · peeringdb.com/net/26568

PeeringDB

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

Make the changes on Telecom Plus'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::c961:1 2001:7f8:4::c961:3
    IPv4 address in PeeringDB, not in the export195.66.225.240 195.66.227.145 195.66.231.74195.66.227.145 195.66.231.74
    Port speed differs2G + 2 × 1G2G + 1G
    • The entry with IPv4 195.66.225.240, IPv6 – isn't in the export: delete it if that connection is gone.
    • In the entry with IPv4 195.66.227.145: set IPv6 to 2001:7f8:4::c961:1 (now empty).
    • In the entry with IPv4 195.66.231.74: set IPv6 to 2001:7f8:4::c961:3 (now empty).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1::c961:2 2001:7f8:4:1::c961:4
    IPv4 address in PeeringDB, not in the export195.66.236.9 195.66.236.216 195.66.236.248195.66.236.9 195.66.236.216
    Port speed differs2G + 2 × 1G2G + 1G
    • In the entry with IPv4 195.66.236.216: set IPv6 to 2001:7f8:4:1::c961:2 (now empty).
    • The entry with IPv4 195.66.236.248, IPv6 – isn't in the export: delete it if that connection is gone.
    • In the entry with IPv4 195.66.236.9: set IPv6 to 2001:7f8:4:1::c961:4 (now empty).

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