packet loss and good speed

SaTiGGeR

Active Member
Joined
Nov 27, 2008
Messages
38
Reaction score
2
Hi Im having major issues with my telkom adsl line! nothing new i've been told its because our exchange is congested and they are working on it!! i have been using pingplotter and speedtest.net to try and get some anderstanding of the technical issues. I get packet loss of up 100% to www.telkom.co.za but i run speedtest.net and get a speed of 3.5 megs per second. i just dont understand how this is possible! perhaps someone out there can enlighten me!!
Thanks
Harry
 
Hi Im having major issues with my telkom adsl line! nothing new i've been told its because our exchange is congested and they are working on it!! i have been using pingplotter and speedtest.net to try and get some anderstanding of the technical issues. I get packet loss of up 100% to www.telkom.co.za but i run speedtest.net and get a speed of 3.5 megs per second. i just dont understand how this is possible! perhaps someone out there can enlighten me!!
Thanks
Harry

First of all, dont use telkom.co.za for pinging, that website sucks use www.mybroadband.co.za.

Are you pinging or trace routing?


Try this in CMD tracert www.mybroadband.co.za
 
@SaTiGGeR

See attached pic. Need to open command prompt window as shown.

Tracert route.jpg

If you see hop2 having a large timing number then you can be shure of congested exchange.
Timing numbers should be less >12ms for a good exchange.
 
Last edited:
Hi Im having major issues with my telkom adsl line! nothing new i've been told its because our exchange is congested and they are working on it!! i have been using pingplotter and speedtest.net to try and get some anderstanding of the technical issues. I get packet loss of up 100% to www.telkom.co.za but i run speedtest.net and get a speed of 3.5 megs per second. i just dont understand how this is possible! perhaps someone out there can enlighten me!!
Thanks
Harry


Good thing I wrote an essay on this the other day

http://mybroadband.co.za/vb/showthread.php/621501-Detecting-a-congested-ADSL-exchange-Guide
 
@SaTiGGeR

See attached pic. Need to open command prompt window as shown.

View attachment 123791

If you see hop2 having a large timing number then you can be shure of congested exchange.
Timing numbers should be less >12ms for a good exchange.

Your exchange isnt congested, only if you see figures like below then your exchange is congested.

PS: When uploading a picture untick the box you see if you are doing it via URL.

59d3671a2d.png
 
Thanks for all the input guys!!Did a tracert and got "Request timed out" on the second hop to the exchange. Does that mean my ping or trce is not even getting to the exchange?
Also read somewhere that the dslam is congested and have swung me over to the Imax but there is bo sparesfor the imax!!Have heard that the new technology Is A Msan! Is that good and does anyone have any idea when that will be
Cheers for all the Input Guys
 
@SatiGGer

When the moved me over from the old house to MASM.I also could not get second hop readings (time out). Don't know if this is applicable?
From 3rd hop onwards you should get some sort of timing results.The also should be low.
Depends were tracert ends. Local should be >15ms. Cape Town >45ms and International >220ms. Thumb suck figures.

If you don't get any readings at all could be your firewall prevents you.
 
Last edited:
I've had great internet for a few months - in the last 2 days its been dismal. Funilly enough Telkom has been calling me for the past week telling me my area is upgrading to fibre and pushing me to sign up... then this happens.

Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.lan [192.168.10.1]
2 1446 ms 1481 ms 1565 ms 196-215-207-1.dynamic.isadsl.co.za [196.215.207.1]
3 1646 ms 1716 ms 1721 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 1804 ms 1889 ms 1909 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 1951 ms 2004 ms 2007 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
6 2241 ms 1435 ms 1397 ms ar2-rba-gi0-1.ip.isnet.net [168.209.1.172]
7 1797 ms 1387 ms 749 ms mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net [168.209.86.250]
8 629 ms 863 ms 940 ms 197.96.148.74
9 1239 ms 1221 ms 1264 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.151]
10 1043 ms 828 ms 722 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.246]
11 511 ms 566 ms 440 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
12 452 ms 498 ms 526 ms row-access-switch1-row3-4.jnb1.host-h.net [197.189.193.36]
13 558 ms 791 ms 736 ms 197.242.89.170
 
Are you sure they are not upgrading the exchange if they have been calling for you to upgrade to fibre, as unlikely as that seems. You could be lucky and have a new exchange in the next week.
 
I thought the fibre thing was strange too, but I checked their website and I fall in the fibre roll-out zone. They could be upgrading the exchange, but the exchange was upgraded a few months ago (before which I also had congestion issues - also my max speed as indicated on my router went from 5mb to 27mb).

I'm checking this morning for the first time (only been online at night recently) and the speeds are fine. Seems to be some massve congestion at night then?
 
Thanks for all the help guys problem has been found!! ironically it was a program i was using to try and help me solve my problem that was causing the problem.Pingplotter or rather my modem was doing this
"Typically, when we receive reports like this, the culprit is a router that isn't particularly fond of multiple outstanding ICMP echo requests" this was the reaponse from ping plotter when i asked their technical team, so suppose it wasnt really pingplotter but my modem Netgear dgn2200mv2. thers a link to work around this issue if you need to
Thanks Again
Harry
 
Top
Sign up to the MyBroadband newsletter
X