That's pretty odd.
Is the latency replicated in a traceroute too?
Yes it is. But appears to be isolated to SAIX, as Mweb is also ok, around 25ms.
Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 * * * Request timed out.
3 25 ms 25 ms 25 ms 41.181.54.85
4 25 ms 25 ms 25 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
5 60 ms 33 ms 31 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 35 ms 32 ms 32 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 26 ms 26 ms 26 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 32 ms 66 ms 32 ms 196.44.0.74
9 26 ms 28 ms 29 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
10 29 ms 30 ms 31 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
11 34 ms 34 ms 34 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
12 34 ms 35 ms 34 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
13 37 ms 37 ms 39 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
14 29 ms 30 ms 28 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 35 ms 35 ms 35 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 28 ms 30 ms 28 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 * * * Request timed out.
3 26 ms 27 ms 26 ms 41.181.221.253
4 38 ms 34 ms 32 ms 41.181.221.254
5 32 ms 32 ms 32 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 32 ms 32 ms 32 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 25 ms 24 ms 24 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
8 * * * Request timed out.
9 176 ms 176 ms 176 ms 196.43.25.205
10 177 ms 176 ms 176 ms 196.43.51.26
11 170 ms 170 ms 169 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
12 177 ms 176 ms 177 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]