TNET Servizi: PeeringDB fix list

AS24749 · peeringdb.com/net/23181

PeeringDB

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

Make the changes on TNET Servizi'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 missing from PeeringDB217.29.67.190217.29.66.115 217.29.67.190 217.29.67.247
    IPv6 address missing from PeeringDB2001:7f8:b:100:1d1:a5d2:4749:1902001:7f8:b:100:1d1:a5d2:4749:115 2001:7f8:b:100:1d1:a5d2:4749:190 2001:7f8:b:100:1d1:a5d2:4749:247
    Port speed differs10G2 × 100G + 10G
    • Add an entry: IPv4 217.29.66.115, IPv6 2001:7f8:b:100:1d1:a5d2:4749:115, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 217.29.67.247, IPv6 2001:7f8:b:100:1d1:a5d2:4749:247, speed 100000 (100G), RS peer yes.

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