Low Bandwidth

[zappaDPJ]

I've started a new thread to try and sort out an issue I'm having. To cut a long story short I've identified I'm having a problem with bandwidth.



My modem stats:

ADSL Link Downstream Upstream
Connection Speed 8128 kbps 448 kbps
Line Attenuation 26.0 db 12.0 db
Noise Margin 6.3 db 23.0 db

My usual throughput on the downstream is around 6.8Mb/s. The current 0.55Mb/s probably explains why I've had high (gaming) pings and websites are currently so slow to resolve.

Any ideas?

[Rik]

Can you do a BT speed test please, Zappa?

[zappaDPJ]

Done

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 8128 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 7150 kbps
    Actual IP throughput achieved during the test was - 831 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or websites please contact your ISP for assistance.

Your test has completed please close this window to exit the performance tester.

[Rik]

Thanks. You need to send that result to IDNet. My instinct is that it's exchange congestion, but they need to look at the line to be sure.

Having just got IDNet to test your line, are you connecting wirelessly? If so, could you try a cable connection, your pings are good, no packet loss, so it may be the wifi connection.

[zappaDPJ]

I'm cabled into the Router. We do make occasional use of WiFi via a laptop but not at the moment. I've also checked that's nothing unknown running in the background on this PC.

It's very odd because up until yesterday or today my downstream which I check around once a week has always been rock solid at 6.8Mb/s.

[Rik]

James was betting on it being a wireless connection. You'd better have a word with support direct, on the face of it the line is fine and ping times to your router (11ms) suggest the exchange is not to blame. As the profile is correct for the sync speed, he'll have to do some more digging.

[zappaDPJ]

Ok thanks for your help Rik, it is much appreciated

I'm going to do a few tests of my own to eliminate any possibility that it's an issue with my equipment and then I'm away for 24 hours or so but I'll give support a ring when I return.

[Rik]

Keep us posted.

[Sebby]

It could just be an unknown glitch, but something is not right, though what exactly is not apparent.

[zappaDPJ]

Well I've tested as much as I can at my end and things are not looking too good.

I've attempted to run the BT speedtest again and this time after completing test one it attempted to complete a further two tests but consistently bails out on test three. It just sits there without ever returning a final result.

My connection is currently running so slowly I can't do anything other than basic browsing and that is painfully slow.

I'll phone support when I get back from work tomorrow.

[cavillas]

Is your telephone line underground or overhead via poles?  There may be a faulty joint/connection.

[zappaDPJ]

Overhead cable and IDNet are currently on the case. My gut feeling is that it's an exchange issue.

[cavillas]

Just thought it could have been a connection joint where cable joins junctions etc.  Sometimes these physical defects cause problems that can be difficult to trace and are often intermittent.

[zappaDPJ]

I certainly wouldn't rule it out. At this stage it doesn't seem like it's a problem with my equipment or anything within IDNet's direct control.

[zappaDPJ]

And fixed.

It was a software problem at my exchange which was limiting throughput on the downstream for me and probably a few hundred other Internet users on the same hardware.

Many thanks to IDNet and particularly James for resolving the problem. I can't give you karma but I can bring quite a large number of soon to be homeless Tiscali/Pipex users your way.

Thanks again 

[Rik]

That's great, Zappa, it certainly explains the mis-match between your stats and throughput. 

[cavillas]

Glad it's sorted for you. and the more the merrier.  More people to share twisted humour with.

[Ray]

That's good, Zappa, glad it's sorted for you. 

[zappaDPJ]

Thanks

[Sebby]

Excellent result.

[zappaDPJ]

Just bumping this thread for visibility as the problem has come back. I was warned this might happen.

I'll phone IDNet in the morning.

[Sebby]

Strange that it should reappear if it was a software error at the exchange. Anyway, get onto IDNet again and hopefully they'll get it sorted again.

[zappaDPJ]

I will do Sebby. The way it was explained to me was that it is an incorrect setting present in software and that the software may reapply the setting at a later date in which case BT would have to find it and change it. I'd take a guess that it overwrites the correct value which has been set from another source.

[Sebby]

Ah, what a pain.

[Rik]

How very BT.

[zappaDPJ]

Well to be fair it does look from the other latency thread that it might actually be a different issue... but let's blame BT anyway 

[Rik]

 

Always a good plan.

[esh]

I had a 6M DSL Verizon line while in Boston. For a period of two weeks I was limited to some measly bandwidth because of a 60% (!) packet loss behaviour (hardly anything would resolve either, obviously), resulting in a frankly unbelievable 110,000 ms ping to some games. They blamed it on our hardware for a week, then eventually came around, poked things, and said it was fine. After really insisting that 60% packet loss was not normal they went away again (curiously the loss only seemed to be upstream). Another week later it was mysteriously all fixed. I wonder if that was an exchange software issue also.

[zappaDPJ]

There seem to be so many variables involved it's hard to say but it's certainly a possibility I guess. High packet loss seems to go hand in hand with exchange congestion which ultimately gives you ridiculously high pings especially when measured over time.