Southern Phone Company
AS136994 · 136994
Southern Phone Company Ltd
Tools: Where can I peer with Southern Phone Company? · Where should Southern Phone Company peer next? · Compare Southern Phone Company with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in Southern Phone Company's PeeringDB record, from what its exchanges publish: 2 to add, 4 to correct, 1 to check. As of 2026-11-19 12:40 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 (2)
On the exchange's own member list, but not in Southern Phone Company's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 218.100.76.102 IPv6 2001:7fa:11:2:0:1722:0:1 Speed 40000 Mbps (40G) 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.
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.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 218.100.52.236 218.100.52.40 218.100.52.236 IPv6 address missing from PeeringDB 2001:7fa:11:4:2:1722:0:1 2001:7fa:11:4:2:1722:0:1 2001:7fa:11:4:2:1722:0:2 Port speed differs 100G 2 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 103.26.71.125 103.26.71.125 103.26.71.142 IPv6 address missing from PeeringDB 2001:dea:0:30::7d 2001: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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 103.26.68.227 103.26.68.18 103.26.68.227 IPv6 address missing from PeeringDB 2001:dea:0:10::e3 2001: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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Southern Phone Company has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 202.12.243.45 IPv6 2001:dea:0:50::2d Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 9 |
| Nov 2, 2026 | 9 |
| Nov 1, 2026 | 9 |
| Oct 31, 2026 | 9 |
| Oct 30, 2026 | 9 |
| Oct 29, 2026 | 9 |
| Oct 28, 2026 | 9 |
| Oct 27, 2026 | 9 |
| Oct 26, 2026 | 9 |
| Oct 25, 2026 | 9 |
| Oct 24, 2026 | 9 |
| Oct 23, 2026 | 9 |
| Oct 22, 2026 | 9 |
| Oct 21, 2026 | 9 |
| Oct 20, 2026 | 9 |
| Oct 19, 2026 | 9 |
| Oct 18, 2026 | 9 |
| Oct 17, 2026 | 9 |
| Oct 16, 2026 | 9 |
| Oct 15, 2026 | 9 |
| Oct 14, 2026 | 9 |
| Oct 13, 2026 | 9 |
| Oct 12, 2026 | 9 |
| Oct 11, 2026 | 9 |
| Oct 10, 2026 | 9 |
| Oct 9, 2026 | 9 |
| Oct 8, 2026 | 9 |
| Oct 7, 2026 | 9 |
| Oct 6, 2026 | 9 |
| Oct 5, 2026 | 9 |
| Oct 4, 2026 | 9 |
| Oct 3, 2026 | 9 |
In the last 30 days Southern Phone Company joined 0 exchanges and left 1. Growing networks
Left
- MegaIX Brisbane Brisbane Nov 4, 2026
Map
Where Southern Phone Company's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| EdgeIX - Sydney Sydney, Australia | Not in PeeringDB | ||
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 40G | Not in PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 100G | Both | |
| IX Australia Perth (WA-IX) Perth, Australia | 10G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MegaIX Melbourne Melbourne, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MegaIX Perth Perth, Australia | 10G | PeeringDB only | |
| MegaIX Sydney Sydney, Australia | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB |
Southern Phone Company lists no facilities in PeeringDB.
Recent changes Search them
- Nov 4, 2026 [IXF] AS136994 Southern Phone Company left MegaIX Brisbane
- Oct 21, 2026 [IXF] AS136994 Southern Phone Company dropped from MegaIX Perth's IX-F list (still in PeeringDB)