I was phoned just after 3pm today from MWEB, forgot the persons name, to find out if I still have issues with my latency. As I told him, my connection was fine since Saturday morning about 11am up until I went to work at 6am this morning. Telkom did work on the line on Saturday early morning for 2 hours, according to him they also fixed something on Sunday. He will phone me again tomorrow, then I can give him the good news what happened tonight.
Yes, Telkom guest and tiscally. Just because I can, some more results just taken:
C:\Users\Andries>ping mweb.co.za
Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Reply from 196.2.63.110: bytes=32 time=36ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Reply from 196.2.63.110: bytes=32 time=35ms TTL=119
Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms
C:\Users\Andries>tracert mweb.co.za
Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 11 ms 11 ms 197-80-96-161.jhb.mweb.co.za [197.80.96.161]
4 10 ms 10 ms 10 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
5 11 ms 11 ms 11 ms vl-92-vic-hscore-1.mweb.co.za [197.80.2.1]
6 37 ms 39 ms 35 ms tengig-0-0-0-2-11-vic-p-2.mweb.co.za [197.80.5.2
26]
7 35 ms 34 ms 32 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
8 34 ms 34 ms 34 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
9 38 ms 35 ms 34 ms 196.28.178.66
10 40 ms 34 ms 39 ms cte-core-sw2.vwol.net [196.41.144.35]
11 36 ms 38 ms 43 ms
www.mweb.co.za [196.2.63.110]
Trace complete.