Southern Phone Company: PeeringDB fix list

AS136994 · peeringdb.com/net/20533

PeeringDB

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

Make the changes on Southern Phone Company'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 (3)

On the exchange's own member list, but not in Southern Phone Company'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 Brisbane (QLD-IX) Brisbane, Australia · PeeringDB 576From its IX-F export
    IPv4218.100.76.102
    IPv62001:7fa:11:2:0:1722:0:1
    Speed40000 Mbps (40G)
    RS peerYes

    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 781From its IX-F export
    IPv4103.26.70.108
    IPv62001:dea:0:20::6c
    SpeedNot published
    RS peerYes

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

Correct these entries (4)

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 Perth (WA-IX) Perth, Australia · PeeringDB 21
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 27.106.192.122: 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 Sydney (NSW-IX) Sydney, Australia · PeeringDB 716
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB218.100.52.236218.100.52.40 218.100.52.236
    IPv6 address missing from PeeringDB2001:7fa:11:4:2:1722:0:12001:7fa:11:4:2:1722:0:1 2001:7fa:11:4:2:1722:0:2
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 218.100.52.40, IPv6 2001:7fa:11:4:2:1722:0:2, speed 100000 (100G), 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.

  3. Australia MegaIX Melbourne Melbourne, Australia · PeeringDB 779
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.26.71.125103.26.71.125 103.26.71.142
    IPv6 address missing from PeeringDB2001:dea:0:30::7d2001:dea:0:30::7d 2001:dea:0:30::8e
    • Add an entry: IPv4 103.26.71.142, IPv6 2001:dea:0:30::8e, 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.

  4. Australia MegaIX Sydney Sydney, Australia · PeeringDB 780
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB103.26.68.227103.26.68.18 103.26.68.227
    IPv6 address missing from PeeringDB2001:dea:0:10::e32001:dea:0:10::12 2001:dea:0:10::e3
    • Add an entry: IPv4 103.26.68.18, IPv6 2001:dea:0:10::12, 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/136994/: 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.