ADSL Even worse now

Sonic2k

Sonic2k

Executive Member
Joined
Feb 7, 2011
Messages
7,636
Reaction score
4
I am sorry to report but the moving of the DSLAM only temporarily sorted out the problem...

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:

Request timed out.
Reply from 196.2.63.110: bytes=32 time=1686ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1415ms TTL=111
Reply from 196.2.63.110: bytes=32 time=920ms TTL=111
Reply from 196.2.63.110: bytes=32 time=980ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1376ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1383ms TTL=111
Reply from 196.2.63.110: bytes=32 time=810ms TTL=111
Reply from 196.2.63.110: bytes=32 time=964ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1155ms TTL=111
Request timed out.
Reply from 196.2.63.110: bytes=32 time=757ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1237ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1264ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1129ms TTL=111
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 41.134.65.97: Destination host unreachable.
Reply from 41.134.65.97: Destination host unreachable.
Request timed out.
Reply from 41.134.65.97: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 41.134.65.97: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 41.134.65.97: Destination host unreachable.
Reply from 41.134.65.97: Destination host unreachable.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=799ms TTL=111
Reply from 196.2.63.110: bytes=32 time=918ms TTL=111
Reply from 196.2.63.110: bytes=32 time=600ms TTL=111
Request timed out.
Request timed out.
Reply from 196.2.63.110: bytes=32 time=664ms TTL=111
Reply from 196.2.63.110: bytes=32 time=651ms TTL=111
Reply from 196.2.63.110: bytes=32 time=923ms TTL=111
Request timed out.
Reply from 196.2.63.110: bytes=32 time=1106ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1179ms TTL=111
Reply from 196.2.63.110: bytes=32 time=967ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1302ms TTL=111
Reply from 196.2.63.110: bytes=32 time=973ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1292ms TTL=111
Reply from 196.2.63.110: bytes=32 time=688ms TTL=111
Reply from 196.2.63.110: bytes=32 time=854ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1089ms TTL=111
Reply from 196.2.63.110: bytes=32 time=522ms TTL=111
Reply from 196.2.63.110: bytes=32 time=289ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1003ms TTL=111
Reply from 196.2.63.110: bytes=32 time=501ms TTL=111
Reply from 196.2.63.110: bytes=32 time=421ms TTL=111
Reply from 196.2.63.110: bytes=32 time=698ms TTL=111
Reply from 196.2.63.110: bytes=32 time=335ms TTL=111
Reply from 196.2.63.110: bytes=32 time=708ms TTL=111
Request timed out.
Reply from 196.2.63.110: bytes=32 time=687ms TTL=111
Reply from 196.2.63.110: bytes=32 time=187ms TTL=111
Reply from 196.2.63.110: bytes=32 time=575ms TTL=111
Reply from 196.2.63.110: bytes=32 time=662ms TTL=111
Reply from 196.2.63.110: bytes=32 time=709ms TTL=111
Reply from 196.2.63.110: bytes=32 time=762ms TTL=111
Reply from 196.2.63.110: bytes=32 time=668ms TTL=111
Reply from 196.2.63.110: bytes=32 time=753ms TTL=111
Reply from 196.2.63.110: bytes=32 time=619ms TTL=111
Reply from 196.2.63.110: bytes=32 time=359ms TTL=111
Reply from 196.2.63.110: bytes=32 time=623ms TTL=111
Reply from 196.2.63.110: bytes=32 time=731ms TTL=111
Reply from 196.2.63.110: bytes=32 time=485ms TTL=111
Reply from 196.2.63.110: bytes=32 time=512ms TTL=111
Reply from 196.2.63.110: bytes=32 time=925ms TTL=111
Reply from 196.2.63.110: bytes=32 time=757ms TTL=111
Reply from 196.2.63.110: bytes=32 time=953ms TTL=111
Reply from 196.2.63.110: bytes=32 time=881ms TTL=111
Reply from 196.2.63.110: bytes=32 time=850ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1075ms TTL=111
Reply from 196.2.63.110: bytes=32 time=594ms TTL=111
Reply from 196.2.63.110: bytes=32 time=713ms TTL=111
Reply from 196.2.63.110: bytes=32 time=794ms TTL=111
Reply from 196.2.63.110: bytes=32 time=981ms TTL=111
Reply from 196.2.63.110: bytes=32 time=803ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1039ms TTL=111
Reply from 196.2.63.110: bytes=32 time=767ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1039ms TTL=111
Reply from 196.2.63.110: bytes=32 time=859ms TTL=111
Reply from 196.2.63.110: bytes=32 time=763ms TTL=111
Reply from 196.2.63.110: bytes=32 time=407ms TTL=111
Reply from 196.2.63.110: bytes=32 time=914ms TTL=111
Reply from 196.2.63.110: bytes=32 time=615ms TTL=111
Reply from 196.2.63.110: bytes=32 time=897ms TTL=111
Click to expand...

I am at a loss for words....
 
Nope, the line is with Telkom.... MWEB is just the ISP...
 
Hi Koosi

The reason you received the results above was due to the Seacom cable break. That has been resolved now so please check your connection again and provide me feedback.

Regards,
MWEB Guy
 
OK here goes...

Reply from 196.2.63.110: bytes=32 time=373ms TTL=111
Reply from 196.2.63.110: bytes=32 time=626ms TTL=111
Reply from 196.2.63.110: bytes=32 time=589ms TTL=111
Reply from 196.2.63.110: bytes=32 time=794ms TTL=111
Reply from 196.2.63.110: bytes=32 time=986ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1042ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1047ms TTL=111
Reply from 196.2.63.110: bytes=32 time=768ms TTL=111
Reply from 196.2.63.110: bytes=32 time=818ms TTL=111
Reply from 196.2.63.110: bytes=32 time=580ms TTL=111
Reply from 196.2.63.110: bytes=32 time=828ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1141ms TTL=111
Reply from 196.2.63.110: bytes=32 time=934ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1071ms TTL=111
Reply from 196.2.63.110: bytes=32 time=1024ms TTL=111
Click to expand...

If you look at the IP, you will see I am pinging mweb.co.za, therefore this has nothing to do with the SEACOM cable or does it?
 
Do a traceroute too, it tells a whole lot more than a simple ping. Potentially something like ping plotter to give you the constant ping effect in a traceroute so that you can see where the actual problem is.
 
am just monitoring for now... the line remains up, which is more important than ping lag...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X