ixreport

STEL: PeeringDB fix list

AS56550 · peeringdb.com/net/5444

PeeringDB

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

Make the changes on STEL'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 (3)

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.66.130217.29.66.130 217.29.67.95
    IPv6 address missing from PeeringDBnone2001:7f8:b:100:1d1:a5d5:6550:130
    Port speed differs10G100G + 20G
    • In the entry with IPv4 217.29.66.130: set IPv6 to 2001:7f8:b:100:1d1:a5d5:6550:130 (now empty); set Speed to 100000 (100G) (now 10000).
    • Add an entry: IPv4 217.29.67.95, IPv6 –, speed 20000 (20G), RS peer yes.
  2. Italy Namex Rome Rome, Italy · PeeringDB 121
    ProblemPeeringDB hasThe export has
    Port speed differs3G10G
    • In the entry with IPv4 193.201.28.67: set Speed to 10000 (10G) (now 3000).

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

  3. Italy VSIX Padova, Italy · PeeringDB 311
    ProblemPeeringDB hasThe export has
    Port speed differs3G10G
    • In the entry with IPv4 185.1.115.44: set Speed to 10000 (10G) (now 3000).

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

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