VSIX Network: PeeringDB fix list

AS2593 · peeringdb.com/net/2742

PeeringDB

4 things to fix in VSIX Network's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on VSIX Network'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 (4)

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 MINAP Milan Milan, Italy · PeeringDB 240
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.114.15: set Speed to 100000 (100G) (now 10000).

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

  2. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 217.29.67.110: set Speed to 100000 (100G) (now 10000).
  3. Italy TOP-IX Turin, Italy · PeeringDB 115
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 194.116.96.150: set Speed to 100000 (100G) (now 20000).

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

  4. Italy VSIX Padova, Italy · PeeringDB 311
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.115.1: set Speed to 200000 (200G) (now 10000).

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