ixreport

Aire Networks del Mediterraneo: PeeringDB fix list

AS29119 · peeringdb.com/net/3136

PeeringDB

3 things to fix in Aire Networks del Mediterraneo's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Aire Networks del Mediterraneo's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in Aire Networks del Mediterraneo's PeeringDB record. Add one entry per connection with these values.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.192.113
    IPv62001:7f8::71bf:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.227.74
    IPv62a03:5f80:4::227:74
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.236.126
    IPv62a03:5f80:4:2::236:126
    Speed100000 Mbps (100G)
    RS peerYes

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

Correct these entries (1)

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
    Address belongs to another network in PeeringDB80.81.192.113 is AS34120 Verslo Tiltas80.81.192.113

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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