SkyMesh: PeeringDB fix list

AS7477 · peeringdb.com/net/3213

PeeringDB

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

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

  1. Australia EdgeIX - Sydney Sydney, Australia · PeeringDB 2761From its website members list
    IPv4202.77.88.119
    IPv62001:df0:680:5::76
    SpeedNot published
    RS peerNot published

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 Brisbane (QLD-IX) Brisbane, Australia · PeeringDB 576
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 218.100.76.20: set Speed to 20000 (20G) (now 10000).

    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 Melbourne (VIC-IX) Melbourne, Australia · PeeringDB 513
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G + 1G
    • In the entry with IPv4 218.100.78.60: set Speed to 1000 (1G) (now 10000).

    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
    IPv4 address missing from PeeringDB103.26.68.36103.26.68.36 103.26.69.15
    IPv6 address missing from PeeringDB2001:dea:0:10::242001:dea:0:10::24 2001:dea:0:10::10f
    • Add an entry: IPv4 103.26.69.15, IPv6 2001:dea:0:10::10f, RS peer yes.

    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/7477/: 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.