Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\user>tracert bras.afrihost.co.za
Unable to resolve target system name bras.afrihost.co.za.
C:\Users\user>tracert 155.239.255.250
Tracing route to 155.239.255.250 over a maximum of 30 hops
1 7 ms <1 ms 69 ms 192.168.0.1
2 506 ms 537 ms 301 ms 169-0-62-1-access.afrihost.co.za [169.0.62.1]
3 1321 ms 672 ms 2044 ms ipc-rx-b-access.afrihost.co.za [169.1.1.238]
4 1539 ms 423 ms 99 ms 41.170.79.236
5 2167 ms 1467 ms 278 ms 41.160.2.33
6 1466 ms 2597 ms 2557 ms 41.160.2.69
7 2640 ms 2266 ms 2566 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
8 196.43.26.106 reports: Destination host unreachable.
Trace complete.
C:\Users\user>ping 155.239.255.250
Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\user>
This looks like really horrible exchange congestion to me. The second hop is off Telkom's BRAS, clearly a backhaul issue here or a line fault causing high latency