ixreport

Cerberus Networks Ltd: PeeringDB fix list

AS51918 · peeringdb.com/net/4004

PeeringDB

3 things to fix in Cerberus Networks Ltd's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Cerberus Networks Ltd'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 differs10G + 1G4G + 2G
    • In the entry with IPv4 195.66.225.163: set Speed to 4000 (4G) (now 10000).
    • In the entry with IPv4 195.66.226.163: set Speed to 2000 (2G) (now 1000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 195.66.237.163: set Speed to 10000 (10G) (now 1000).
  3. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 1G10G + 5G
    • In the entry with IPv4 5.57.80.204: set Speed to 5000 (5G) (now 1000).
    • In the entry with IPv4 5.57.80.205: set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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