High Tide Group: PeeringDB fix list

AS211501 · peeringdb.com/net/26570

PeeringDB

3 things to fix in High Tide Group's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on High Tide Group'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 (3)

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
    Port speed differs1G2G
    • In the entry with IPv4 195.66.227.94: set Speed to 2000 (2G) (now 1000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G
    • In the entry with IPv4 195.66.236.197: set Speed to 2000 (2G) (now 1000).
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs1G2G
    • In the entry with IPv4 195.66.244.91: set Speed to 2000 (2G) (now 1000).

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