ixreport

Hyperwave

AS135406 · Hyperwave

BCD NETWORKS PTY LTD

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Hyperwave? · Where should Hyperwave peer next? · Compare Hyperwave with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Hyperwave's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 18:41 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. 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. 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20265
Show as a table
DateExchanges
Nov 19, 20265
Nov 18, 20265
Nov 17, 20265
Nov 16, 20265
Nov 15, 20265
Nov 14, 20265
Nov 13, 20265
Nov 12, 20265
Nov 11, 20265
Nov 10, 20265
Nov 9, 20265
Nov 8, 20265
Nov 7, 20265
Nov 6, 20265
Nov 5, 20265
Nov 4, 20265
Nov 3, 20265
Nov 2, 20265
Nov 1, 20265
Oct 31, 20265
Oct 30, 20265
Oct 29, 20265
Oct 28, 20265
Oct 27, 20265
Oct 26, 20265
Oct 25, 20265
Oct 24, 20265
Oct 23, 20265
Oct 22, 20265
Oct 21, 20265
Oct 20, 20265
Oct 19, 20265
Oct 18, 20265
Oct 17, 20265
Oct 16, 20265
Oct 15, 20265
Oct 14, 20265
Oct 13, 20265
Oct 12, 20265
Oct 11, 20265
Oct 10, 20265
Oct 9, 20265
Oct 8, 20265
Oct 7, 20265
Oct 6, 20265
Oct 5, 20265
Oct 4, 20265
Oct 3, 20265

Map

Where Hyperwave's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 32G across 5 exchanges.

Australia EdgeIX - Melbourne Melbourne, Australia 202.77.90.32 10G Yes PeeringDB
Australia EdgeIX - Sydney Sydney, Australia 202.77.88.70 1G Yes Both
Australia IX Australia Melbourne (VIC-IX) Melbourne, Australia 218.100.78.96 10G Yes Both IPv6 not in PeeringDB
Australia IX Australia Sydney (NSW-IX) Sydney, Australia 218.100.52.59 1G Yes Both IPv6 not in PeeringDBSpeed differs
Australia MegaIX Melbourne Melbourne, Australia 103.26.71.146 10G Yes Both IPv6 not in PeeringDB

Hyperwave lists no facilities in PeeringDB.