Aptus Solutions Ltd: PeeringDB fix list
AS37349 · peeringdb.com/net/4094
2 things to fix in Aptus Solutions Ltd's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Aptus Solutions Ltd's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (1)
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 IPv4 address missing from PeeringDB 196.60.8.71 196.60.8.71 196.60.9.36 IPv6 address missing from PeeringDB 2001:43f8:6d0::71 2001:43f8:6d0::71 2001:43f8:6d0::9:36 Port speed differs 10G 2 × 10G - Add an entry: IPv4 196.60.9.36, IPv6 2001:43f8:6d0::9:36, speed 10000 (10G), 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 Aptus Solutions Ltd has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.60.124.124 IPv6 2001:43f8:1771::91e5:1 Speed 10000 Mbps (10G)
From ixreport.com/net/37349/: 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.