ixreport

Hyperwave: PeeringDB fix list

AS135406 · peeringdb.com/net/15722

PeeringDB

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

Make the changes on Hyperwave'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. Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:1:2:10ee:0:1
    • In the entry with IPv4 218.100.78.96: set IPv6 to 2001:7fa:11:1:2:10ee: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.

  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:2:10ee:0:1
    Port speed differs1G100M
    • In the entry with IPv4 218.100.52.59: set IPv6 to 2001:7fa:11:4:2:10ee:0:1 (now empty); set Speed to 100 (100M) (now 1000).

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

  3. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:30::92
    • In the entry with IPv4 103.26.71.146: set IPv6 to 2001:dea:0:30::92 (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/135406/: 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.