Cilix Limited: PeeringDB fix list

AS215638 · peeringdb.com/net/35181

PeeringDB

4 things to fix in Cilix Limited's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on Cilix 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 (4)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G400G
    • In the entry with IPv4 80.81.194.41: set Speed to 400000 (400G) (now 10000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G40G
    • In the entry with IPv4 178.18.226.61: set Speed to 40000 (40G) (now 100000).
    • In the entry with IPv4 178.18.236.251: set Speed to 40000 (40G) (now 100000).

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

  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs30G20G
    • In the entry with IPv4 195.66.231.224: set Speed to 20000 (20G) (now 30000).
  4. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs30G40G
    • In the entry with IPv4 195.66.236.88: set Speed to 40000 (40G) (now 30000).

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