NetVault: PeeringDB fix list

AS56294 · peeringdb.com/net/13898

PeeringDB

5 things to fix in NetVault's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on NetVault's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in NetVault's PeeringDB record. Add one entry per connection with these values.

  1. Australia IX Australia Perth (WA-IX) Perth, Australia · PeeringDB 21From its IX-F export

    2 connections, so 2 entries:

    IPv427.106.192.108
    IPv62001:7fa:11::db96:0:1
    Speed10000 Mbps (10G)
    RS peerYes
    IPv427.106.192.109
    IPv62001:7fa:11::db96:0:2
    Speed10000 Mbps (10G)
    RS peerYes

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

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. Australia IX Australia Brisbane (QLD-IX) Brisbane, Australia · PeeringDB 576
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:2:0:db96:0:1 2001:7fa:11:2:0:db96:0:2
    • In the entry with IPv4 218.100.76.56: set IPv6 to 2001:7fa:11:2:0:db96:0:1 (now empty).
    • In the entry with IPv4 218.100.76.58: set IPv6 to 2001:7fa:11:2:0:db96:0:2 (now empty).

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

  2. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:1:0:db96:0:1 2001:7fa:11:1:0:db96:0:2
    • In the entry with IPv4 218.100.78.63: set IPv6 to 2001:7fa:11:1:0:db96:0:1 (now empty).
    • In the entry with IPv4 218.100.78.64: set IPv6 to 2001:7fa:11:1:0:db96:0:2 (now empty).

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

  3. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:dbe6:0:1 2001:7fa:11:4:0:dbe6:0:2
    Port speed differs2 × 10G10G
    • In the entry with IPv4 218.100.52.123: set IPv6 to 2001:7fa:11:4:0:dbe6:0:2 (now empty).
    • In the entry with IPv4 218.100.52.131: set IPv6 to 2001:7fa:11:4:0:dbe6:0:1 (now empty).

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If NetVault has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.225.150
    IPv6–
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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