Sky Italia AS60772: PeeringDB fix list

AS60772 · peeringdb.com/net/15130

PeeringDB

One thing to fix in Sky Italia AS60772's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Sky Italia AS60772'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 (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-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export217.29.66.144 217.29.66.173 217.29.68.144 217.29.68.173217.29.66.144 217.29.66.173
    IPv6 address in PeeringDB, not in the export2001:7f8:b:100:1d1:a5d6:772:144 2001:7f8:b:100:1d1:a5d6:772:173 2001:7f8:b:101:1d1:a5d6:772:144 2001:7f8:b:101:1d1:a5d6:772:1732001:7f8:b:100:1d1:a5d6:772:144 2001:7f8:b:100:1d1:a5d6:772:173
    Port speed differs4 × 20G2 × 10G
    • In the entry with IPv4 217.29.66.144: set Speed to 10000 (10G) (now 20000).
    • In the entry with IPv4 217.29.66.173: set Speed to 10000 (10G) (now 20000).
    • The entry with IPv4 217.29.68.144, IPv6 2001:7f8:b:101:1d1:a5d6:772:144 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 217.29.68.173, IPv6 2001:7f8:b:101:1d1:a5d6:772:173 isn't in the export: delete it if that connection is gone.

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