ixreport

Airgrid: PeeringDB fix list

AS201198 · peeringdb.com/net/17271

PeeringDB

3 things to fix in Airgrid's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Airgrid'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 Airgrid's PeeringDB record. Add one entry per connection with these values.

  1. Italy MIX-IT Milan, Italy · PeeringDB 35From its IX-F export
    IPv4217.29.66.117
    IPv6–
    Speed100000 Mbps (100G)
    RS peerYes
  2. Italy Namex Rome Rome, Italy · PeeringDB 121From its IX-F export
    IPv4193.201.28.195
    IPv62001:7f8:10::20:1198
    Speed10000 Mbps (10G)
    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. Italy MIX Bologna Bologna, Italy · PeeringDB 3730
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:101:13::13
    • In the entry with IPv4 185.1.231.13: set IPv6 to 2001:7f8:101:13::13 (now empty).

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