YourDC: PeeringDB fix list

AS134688 · peeringdb.com/net/13535

PeeringDB

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

Make the changes on YourDC'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 (2)

On the exchange's own member list, but not in YourDC'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.

  2. Australia IX Australia Sydney (NSW-IX) Sydney, Australia · PeeringDB 716From 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 (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 Adelaide (SA-IX) Adelaide, Australia · PeeringDB 691
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7fa:11:3:2:e20:0:2
    • In the entry with IPv4 218.100.54.43: set IPv6 to 2001:7fa:11:3:2:e20: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 MegaIX Adelaide Adelaide, Australia · PeeringDB 4506
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:60::e
    • In the entry with IPv4 103.48.48.14: set IPv6 to 2001:dea:0:60::e (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 Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:dea:0:10::153
    • In the entry with IPv4 103.26.69.83: set IPv6 to 2001:dea:0:10::153 (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/134688/: 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.