Showing results for 
Search instead for 
Did you mean: 
Distinguished Guru
Message 11 of 14

Re: Recent slow down.


@Nick2010 wrote:

Aye, DS thats the one, although it doesnt even load the page - just goes blank.

It's been playing up for a while nowSmiley Mad



You may or may not of noticed this bit when you try to run it?


speedtester app'.PNG


Also the main test screen gives you a red bar?

It should be green!


Due to


 Download speedachieved during the test was - 400 Kbps
 For your connection, the acceptable range of speeds is 600-7150 Kbps.


the speed falling below the acceptable range........

-+-No longer a forum member-+-
0 Ratings
Message 12 of 14

Re: Recent slow down.

Speed test results from couple of minutes ago. Still seems to be running pretty slow. Also below are router stats, there seems to be a lot of errors there - not sure what they are though.




 Download speedachieved during the test was - 1361 Kbps
 For your connection, the acceptable range of speeds is 600-7150 Kbps.
 Additional Information:
 Your DSL Connection Rate :6240 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
 IP Profile for your line is - 4500 Kbps




Router Stats Again


ADSL line status
Connection Information
Line stateConnected
Connection time0 days, 15:23:18
Downstream6,240 Kbps
Upstream448 Kbps
ADSL Settings
ModulationG.992.1 Annex A
Latency typeInterleaved
Noise margin (Down/Up)9.6 dB / 24.0 dB
Line attenuation (Down/Up)34.2 dB / 19.0 dB
Output power (Down/Up)9.8 dBm / 1.8 dBm
Loss of Framing (Local/Remote)0 / 0
Loss of Signal (Local/Remote)0 / 0
Loss of Power (Local/Remote)0 / 0
FEC Errors (Down/Up)15001 / 6
CRC Errors (Down/Up)94 / 2
HEC Errors (Down/Up)1691 / 0
Error Seconds (Local/Remote)57 / 5
0 Ratings
Recognised Expert
Message 13 of 14

Re: Recent slow down.

I would try another modem/router if possible as stats and profile all look fair   and its straw clutching time

If any post helps tick the star box on the left
Just cause Im paranoid dont mean they are not out to get me

0 Ratings
Message 14 of 14

Re: Recent slow down.

If your line was 100% healthy ... and not many are ...  😉


It would be capable of IP6500 at that loop loss .... at target 6db noise margin with good bitloading.


Yours is running at 9.6db margin, which is ok, and well in "normal" noise level threshold, but the extra margin


will slow things a little. So there's the first deficit ... maybe 500-700kbps in throughput.


Some of the line errors are common but not ideal, the CRCs, cyclic redundancy checks are total resent packets


and HEC errors are major header corrections for atm packets .... both these types of errors in high numbers


suggest the line is only "average" in condition .... but not unusual.  That is the second deficiency ....


The FEC errors are normal and are interleave corrections, for packet errors.


The error seconds are the amount of total second counts whereby "fairly serious" errors occurred, and as you


can see, a lot were local errors, maybe from local induced noise.


When you add up the "deficiencies" ... they soon rack up, and the bulk of which would account for the deficit


you see, along with maybe some dslam contention that may be there .....


You can't do anything about the line in general, unless it's crackly, and my guess is, it's not, otherwise margin


would be higher, likewise any dslam contention, but you could maybe try careful cable segregation, and get


power cables well away from data .... and keep the hub and cable well away from electrical sources.


Maybe a fully screened and shrouded router cable might help. This would help bring down the margin to target


6db ... and also help bitloading, and make for less errors ... helping things all round.


Try a few things, with a tidy up .... I'd be surprised if you didn't get IP5500, with a little work.


Some things to try here ....


Keep an eye for any improvements in throughput ... and if things don't improve radically after a few days ..


it may be worth getting the exchange side investigated by the moderators ....  😉

0 Ratings