Southern Communications: PeeringDB fix list
AS59395 · peeringdb.com/net/6666
4 things to fix in Southern Communications'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 Southern Communications'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 Southern Communications's PeeringDB record. Add one entry per connection with these values.
-
LINX Manchester Manchester, United Kingdom · PeeringDB 583From its IX-F export and website members listIPv4 195.66.244.141 IPv6 2001:7f8:4:2::e803:1 Speed 4000 Mbps (4G) RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 100G 30G - In the entry with IPv4 195.66.224.102: set Speed to 30000 (30G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 30G - In the entry with IPv4 195.66.236.102: set Speed to 30000 (30G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 40G - In the entry with IPv4 5.57.82.170: set Speed to 40000 (40G) (now 100000).
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/59395/: 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.