ixreport

Clouvider: PeeringDB fix list

AS62240 · peeringdb.com/net/7115

PeeringDB

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

Make the changes on Clouvider'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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G140G + 110G
    • In the entry with IPv4 195.66.225.184: set Speed to 110000 (110G) (now 100000).
    • In the entry with IPv4 195.66.227.14: set Speed to 140000 (140G) (now 100000).
  2. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    Port speed differs100G60G
    • In the entry with IPv4 195.66.244.12: set Speed to 60000 (60G) (now 100000).
  3. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    Port speed differs10G25G
    • In the entry with IPv4 206.41.105.26: set Speed to 25000 (25G) (now 10000).
  4. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs200G25G
    • In the entry with IPv4 185.0.21.45: set Speed to 25000 (25G) (now 200000).

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