I think you both are confused
1. The ip address 154.0.3.106 is in fact on a London router (I am sure @PBCool knows this)
2. Latency and routing between A360 and CISP looks fine at JHB.
--> Looks like A360 doesn't peer at Nap, they use seacom, and seacom and cisp routes fine between each other at nap when looking at traceroutes from both sides.
@cavedog, rather do a traceroute to a CISP IP address, like
www.cisp.co.za / 154.0.13.95
Code:
~ # mtr --report-wide --show-ips 160.20.252.129
Start: Sat Jan 13 12:52:19 2018
HOST: monitor.heaven.za.net Loss% Snt Last Avg Best Wrst StDev
1.|-- router.heaven.za.net (192.168.241.1) 0.0% 10 0.5 0.5 0.4 0.5 0.0
2.|-- 155.93.251.1 0.0% 10 1.3 1.5 1.3 2.6 0.0
3.|-- 154.0.1.125 0.0% 10 1.2 1.2 1.0 1.3 0.0
4.|-- 154.0.1.13 0.0% 10 1.3 1.5 1.3 1.7 0.0
5.|-- seacom.ixp.capetown (196.10.140.66) 0.0% 10 2.1 2.5 2.0 4.9 0.6
6.|-- ae-2.cr-02-cpt.za.seacomnet.com (105.16.30.2) 0.0% 10 20.9 20.6 18.8 22.4 1.1
7.|-- xe-0-0-0-8.cr-02-jnb.za.seacomnet.com (105.16.9.181) 0.0% 10 21.9 21.2 19.2 22.8 1.0
8.|-- xe-0-0-0-0.er-02-jnb.za.seacomnet.com (105.16.28.10) 0.0% 10 18.6 18.7 18.5 19.9 0.3
9.|-- 105.22.42.106 0.0% 10 18.5 18.7 18.5 19.2 0.0
10.|-- 160.20.252.5 0.0% 10 18.6 18.7 18.5 18.9 0.0
11.|-- 160.20.252.129 0.0% 10 20.9 21.6 20.9 22.8 0.3