ixreport

Cloud Nord Limited: PeeringDB fix list

AS215262 · peeringdb.com/net/40283

PeeringDB

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

Make the changes on Cloud Nord 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 (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 differs10G4G
    • In the entry with IPv4 195.66.228.116: set Speed to 4000 (4G) (now 10000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs10G4G
    • In the entry with IPv4 195.66.237.36: set Speed to 4000 (4G) (now 10000).
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G4G + 2G
    • In the entry with IPv4 195.66.244.139: set Speed to 2000 (2G) (now 10000).
    • In the entry with IPv4 195.66.244.140: set Speed to 4000 (4G) (now 10000).

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