ixreport

DALnet IRC Network: PeeringDB fix list

AS31800 · peeringdb.com/net/3

PeeringDB

7 things to fix in DALnet IRC Network's PeeringDB record, from what its exchanges publish: 1 to add, 6 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on DALnet IRC Network'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 DALnet IRC Network's PeeringDB record. Add one entry per connection with these values.

  1. Australia EdgeIX - Sydney Sydney, Australia · PeeringDB 2761From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (6)

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:94d4:0:1
    Port speed differs1G200G
    • In the entry with IPv4 218.100.52.34: set IPv6 to 2001:7fa:11:4:0:94d4:0:1 (now empty); set Speed to 200000 (200G) (now 1000).

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

  2. New Zealand MegaIX Auckland Auckland, New Zealand · PeeringDB 984
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:40::33
    • In the entry with IPv4 43.243.22.51: set IPv6 to 2001:dea:0:40::33 (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 MegaIX Brisbane Brisbane, Australia · PeeringDB 781
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:20::4d
    • In the entry with IPv4 103.26.70.77: set IPv6 to 2001:dea:0:20::4d (now empty).

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

  4. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:30::79
    • In the entry with IPv4 103.26.71.121: set IPv6 to 2001:dea:0:30::79 (now empty).

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

  5. Australia MegaIX Perth Perth, Australia · PeeringDB 1235
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:50::2a
    • In the entry with IPv4 202.12.243.42: set IPv6 to 2001:dea:0:50::2a (now empty).

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

  6. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::c8
    • In the entry with IPv4 103.26.68.200: set IPv6 to 2001:dea:0:10::c8 (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/31800/: 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.