ixreport

Adamo Telecom Iberia S.A: PeeringDB fix list

AS35699 · peeringdb.com/net/1989

PeeringDB

3 things to fix in Adamo Telecom Iberia S.A's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Adamo Telecom Iberia S.A'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. Spain CATNIX Barcelona, Spain · PeeringDB 62
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 193.242.98.143: set Speed to 100000 (100G) (now 20000).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.131.11: set Speed to 200000 (200G) (now 10000).
  3. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G200G + 100G
    • In the entry with IPv4 185.1.192.1: set Speed to 200000 (200G) (now 100000).

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