That trace looks fine. Absa is probably not using a service that is hosted on edge locations like CPT/JHB, but rather a service in a data center, which uses a region like eu-west-1 by the looks of the latency on that trace.
Edit: in fact a dns lookup confirms it:
Code:~ # dig www.absa.co.za ; <<>> DiG 9.12.1-P2 <<>> www.absa.co.za ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60263 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.absa.co.za. IN A ;; ANSWER SECTION: www.absa.co.za. 522 IN CNAME absa-prod-front-alb2-1785404226.eu-west-1.elb.amazonaws.com. absa-prod-front-alb2-1785404226.eu-west-1.elb.amazonaws.com. 44 IN A 54.246.209.253 absa-prod-front-alb2-1785404226.eu-west-1.elb.amazonaws.com. 44 IN A 34.246.6.144 absa-prod-front-alb2-1785404226.eu-west-1.elb.amazonaws.com. 44 IN A 54.171.19.102 ;; Query time: 9 msec ;; SERVER: 172.18.7.33#53(172.18.7.33) ;; WHEN: Thu Jul 26 11:53:15 SAST 2018 ;; MSG SIZE rcvd: 153
Thank you for the extra information.
