That response looks good.
Others have seen their experience improve, let's give a bit more time.
Still have **** latency.
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 52 ms 48 ms 47 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 78 ms 75 ms 77 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 51 ms 54 ms 54 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 80 ms 75 ms 73 ms adept.ct1.napafrica.net [196.10.140.72]
7 63 ms 78 ms 62 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 65 ms 66 ms 65 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 59 ms 55 ms 55 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 89 ms 77 ms 106 ms ql.kreaper.co.za [196.44.45.98]
This route was 18-20 ms before it broke.
Here's bras:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms