EI TOWERS: PeeringDB fix list

AS34599 · peeringdb.com/net/25463

PeeringDB

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

Make the changes on EI TOWERS'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.112217.29.67.112 217.29.67.118
    IPv6 address missing from PeeringDBnone2001:7f8:b:100:1d1:a5d3:4599:112 2001:7f8:b:100:1d1:a5d3:4599:118
    Port speed differs20G2 × 20G
    • In the entry with IPv4 217.29.67.112: set IPv6 to 2001:7f8:b:100:1d1:a5d3:4599:112 (now empty).
    • Add an entry: IPv4 217.29.67.118, IPv6 2001:7f8:b:100:1d1:a5d3:4599:118, speed 20000 (20G), RS peer yes.

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