Would switching ISP help

R

ReenenLaurie

Active Member
Joined
Sep 24, 2011
Messages
85
Reaction score
0
I am currently with Telkom as my ISP, and I have constant ping issues (500-1000+ until about 23:30, when it starts to stabilize).

So the way I understand Mweb/Axxess/Web Africa/etc would still be using the line from Telkom, so I don't think moving from one ISP to another would improve the ping. Unless the lag is generated further up the chain than the last connection to my house, I can't fathom why it would make my ping better.

Any of you guys with technical knowledge could you explain (if so) why my ping would be better with another ISP.

Also a somewhat related question: What is a port reset, and why does it sometimes have a short term improvement to my connection?
 
-Were do you live?
-Whats your first 6 digits of your land line number?
-Whats your router stats?

Its probably your exchange, its congested.
 
Download winmtr and run it when you have issues & no issues. Post the output of both here so we can compare the good times to the bad http://winmtr.net/

Run it until you've reached at least 100 in the send & receive columns

Also go into your router and post the line statistics here. Looking for things like SNR, Attenuation etc.

Lets first make sure where the problem lies before making recommendations. If it's indeed congestion at the dslam side then there's no point in changing isps.
 
Last edited:
Rickster said:
-Were do you live?
-Whats your first 6 digits of your land line number?
-Whats your router stats?

Its probably your exchange, its congested.
Click to expand...

Durbanville, Cape Town
021 979 xxxx
No idea, I'll check what they are when I get home tonight.

ponder said:
Download winmtr and run it when you have issues & no issues. Post the output of both here so we can compare the good times to the bad http://winmtr.net/

Run it until you've reached at least 100 in the send & receive columns

Also go into your router and post the line statistics here. Looking for things like SNR, Attenuation etc.

Lets first make sure where the problem lies before making recommendations. If it's indeed congestion at the dslam side then there's no point in changing isps.
Click to expand...

I run winmtr, and yeah during "peak" times, min about 300, max 1000+, average 500-600, packet loss 10%+. During "good" times, min 180, max about 380, generally <200, packet loss pretty much 0%. (I ping to 95.172.65.1)

I'll have to get back home for those stats, and I'll check if I can figure out where to find it. Telkom recently (<2weeks ago) worked on the box that's < 300m from my house, but despite that the line speeds are still pretty bad. Our neighbourhood whatsapp group said this "upgrade" enables fibre to the home, but when I spoke to Telkom they said it won't even enable 10mb line in my area.
 
Last edited:
Ok I'm at home, here are the stats (I believe)...

Upstream line rate (kbit/s) : 512
Downstream line rate (kbit/s) : 4096
Upstream maximum line rate (kbit/s) : 1180
Downstream maximum line rate (kbit/s) : 12480
Upstream noise safety coefficient(SNR) (dB) : 26
Downstream noise safety coefficient(SNR) (dB) : 19.1
Upstream interleave depth : 0
Downstream interleave depth : 0
Line standard : ADSL_G.dmt
Upstream line attenuation (dB) : 6
Downstream line attenuation (dB) : 7.5
Upstream output power (dBmV) : 12.1
Downstream output power (dBmV) : -0.7
Downstream CRC : 0
Upstream CRC : 0
Downstream FEC : 0
Upstream FEC : 0
Downstream HEC : 0
Upstream HEC : 0
Upstream Total Cells : 0
Downstream Total Cells : 826181997
Upstream Interleave Delay : 0
Downstream Interleave Delay : 0
Channel type : Fast

WinMTR screenshot (of 22:55 today 27/Jul/2015)
F45rreG.png
F45rreG.png

Image says:
Host 95.172.65.1,
15% packet loss,
sent 100,
received 85,
Best 182,
Ave 277,
Worst 566,
last 299
 
Last edited:
Unfortunately those mtr stats are not of much use.

Let your router login with the telkom guest account "guest@telkomadsl" & password is "guest", remove the "" (I think those account details are correct but you can find them all over the forum).

Now do a normal traceroute from the command line to www.telkom.co.za, note your second or third hop address (second one usually does not show.

Example,
Code: 
[root@asterix xxxx]# traceroute www.telkom.co.za
traceroute to www.telkom.co.za (165.143.158.60), 30 hops max, 60 byte packets
 1  gateway (10.0.0.2)  2.016 ms  2.063 ms  2.144 ms
 2  * * *
 3  ipc-1-up.east.dsl.telkomsa.net (105.229.0.21)  61.089 ms  61.834 ms  64.001 ms
<snip>

In my case it's 105.229.0.21, yours will differ. Punch the IP you get into winmtr and test again.

You should also have access to http://capetown.spdtst.saix.net/ to do a speedtest if you want.

In order to test dslam congestion you want to test to the hop closest to you. According to ranger using the guest account is more accurate if I recall correctly. Sorry I should have given you all this info yesterday already, apologies.
 
ponder said:
Sorry I should have given you all this info yesterday already, apologies.
Click to expand...

No problem (I've been living with this for years, so a couple of days aren't making a big difference)!

What is the type of numbers that would suggest congestion? You have 61-64ms just to your dslam? (Like 1/3 of the ping that I get to europe is for the last 300m?)
 
My tracert information:


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

1 <1 ms <1 ms <1 ms 10.0.1.2
2 497 ms 511 ms 518 ms wblv-ip-bb-3.south.dsl.telkomsa.net [105.224.200.1]
3 626 ms 662 ms 653 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 542 ms 382 ms 382 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 545 ms 576 ms 510 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 604 ms 605 ms 603 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.58]

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 181 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| wblv-ip-bb-3.south.dsl.telkomsa.net - 2 | 180 | 176 | 302 | 643 | 925 | 670 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
 
ReenenLaurie said:
My tracert information:


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

1 <1 ms <1 ms <1 ms 10.0.1.2
2 497 ms 511 ms 518 ms wblv-ip-bb-3.south.dsl.telkomsa.net [105.224.200.1]
3 626 ms 662 ms 653 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 542 ms 382 ms 382 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 545 ms 576 ms 510 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 604 ms 605 ms 603 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.58]

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 181 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| wblv-ip-bb-3.south.dsl.telkomsa.net - 2 | 180 | 176 | 302 | 643 | 925 | 670 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
Click to expand...

Exchange is congested.


Cry to telkom, its the only way they will fix it.
 
ReenenLaurie said:
My tracert information:


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

1 <1 ms <1 ms <1 ms 10.0.1.2
2 497 ms 511 ms 518 ms wblv-ip-bb-3.south.dsl.telkomsa.net [105.224.200.1]
3 626 ms 662 ms 653 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 542 ms 382 ms 382 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 545 ms 576 ms 510 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 604 ms 605 ms 603 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.58]

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| No response from host - 100 | 181 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 180 | 0 | 0 | 0 | 0 | 0 |
| wblv-ip-bb-3.south.dsl.telkomsa.net - 2 | 180 | 176 | 302 | 643 | 925 | 670 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
Click to expand...

Assuming you are not throttled for over usage, http://userstats.adsl.saix.net/ & https://secure.telkomsa.net/titracker/ I suggest posting your output here http://mybroadband.co.za/vb/showthread.php/544781-TelkomZA & them PM TelkomZA the same output (pointing to your post) and ask if they could move you to an uncongested dslam/imax/msan or whatever.

Oh, include your phone number & adsl username when you PM TelkomZA
 
Last edited:
Looking like either
1. severe exchange congestion
2. faulty equipment somewhere

Have you check your POTS/ADSL filter?

Unplug all telephones in the house and all ethernet cables from your router excepting the one to your PC. Remove the POTS/ADSL filter and plug the router cable directly into the jack. Do the above tests.

If possible try to loan a router/modem and try the above as well.

This is to rule out any issues on your side.

If the test show the same poor results then it is either a Telkom cable fault, your port at the exchange is faulty or the exchange is congested.
 
MickeyD said:
Have you check your POTS/ADSL filter?
Click to expand...

Is that the little box that's between the router and the telephone point? I haven't tested it, but I have used 2 different ones. But if that was faulty would my internet be fine after about 23:00 at night?

MickeyD said:
If possible try to loan a router/modem and try the above as well.
Click to expand...
Telkom replaced my previous router after repeated complaints about connectivity from my side... So I am on my 2nd.

MickeyD said:
your port at the exchange is faulty or the exchange is congested.
Click to expand...
So they would reset the port, perhaps I suffer from positive bias, but it seems like it helps for about 1 day or so. What exactly does that do?

ponder said:
I suggest posting your output here (...) & them PM TelkomZA the same output (pointing to your post) and ask if they could move you to an uncongested dslam/imax/msan or whatever.
Click to expand...

Yeah I'll be doing that. I usually tweet them, but it's not quite long enough to explain everything in detail.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X