ixreport

Time-Net AS51580: PeeringDB fix list

AS51580 · peeringdb.com/net/8931

PeeringDB

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

Make the changes on Time-Net AS51580'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 (2)

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.170 217.29.68.170217.29.66.170
    IPv6 address in PeeringDB, not in the export2001:7f8:b:100:1d1:a5d5:1580:170 2001:7f8:b:101:1d1:a5d5:1580:1702001:7f8:b:100:1d1:a5d5:1580:170
    • The entry with IPv4 217.29.68.170, IPv6 2001:7f8:b:101:1d1:a5d5:1580:170 isn't in the export: delete it if that connection is gone.
  2. Italy Namex Rome Rome, Italy · PeeringDB 121
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:10::5:1580
    • In the entry with IPv4 193.201.29.27: set IPv6 to 2001:7f8:10::5:1580 (now empty).

    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/51580/: 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.