See hidden discussions | Win great prizes | Get free support
Looks like some of their CPT IP blocks still have access to Seacom:
18.104.22.168 => seacom-cpt1 (22.214.171.124/24) Trace to IP serving the content (found with IPvFoo chrome plugin) tracert 126.96.36.199 Tracing route to cache.google.com [188.8.131.52] over a maximum of 30 hops: 1 12 ms 12 ms 12 ms 172.16.0.1 2 14 ms 13 ms 11 ms 184.108.40.206 3 12 ms 12 ms 13 ms 220.127.116.11 4 14 ms 13 ms 13 ms xe-0-0-2-0.dr-01-cpt.za.seacomnet.com [18.104.22.168] 5 13 ms 11 ms 12 ms cache.google.com [22.214.171.124] Trace complete.
I have two warp configs one warp + and then a normal warp i made for a friend (we use it via wireguard)
The one i made for my friend is being pulled from Seacom
View attachment 1313738
My CISP connection when i terminated the VPN is now connecting to Frankfurt
EDIT: after confirming the above i am back to Kenya
Yea i don't mind as long as it works which it is so all good.Discussions on the network groups is they are doing random announces and changes. Probably relative to what you are seeing.