ixreport

IPSTAR Australia: PeeringDB fix list

AS38172 · peeringdb.com/net/26942

PeeringDB

2 things to fix in IPSTAR Australia's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on IPSTAR Australia'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. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:4:0:951c:0:1
    • In the entry with IPv4 218.100.52.166: set IPv6 to 2001:7fa:11:4:0:951c:0:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::72
    • In the entry with IPv4 103.26.68.114: set IPv6 to 2001:dea:0:10::72 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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