|
do ntl have a min standard
Ok I downgraded in january after been consistently at sub 2meg speeds during daylight hours and evenings. The truth was when the CS agent downgraded me my modem didnt get the signal and was on 10meg up until earlier today. The reason I dont know but I would guess the ubr caused it to be delayed or some other fault.
During this free time on 10mbit I was getting speeds of around 1-3mbit in the evening and 8-10mbit probably for around 5 hours from 3-8am. Rest of day probably hovering 3-5 mbit. Upload speed was always at least 450kbit so it didnt appear from that aspect that upload is saturated at the ubr. I wonder if the downstream was maxed or cpu saturation which can apperently happen.
Well after the downgrade I wasnt too fussed since it is what I am supposed to be on and I assumed I would be seeing close to max speeds most of the day and probably drop to 1mbit in the evenings. But instead it appears I am getting the same proportion of speed in relation to the limit.
I am now seeing around 20-50kB downstream during the evening but with 24kB upstream which I think is max. (not at same time) the modem config confirms I am on a 2meg config and I have seen little bursts to 2meg, I expect early morning I will have no problems reaching 2mbit which will confirm it isnt a pc issue.
this was taken at 11am today
Downstream 1435 Kbps (179.4 KB/sec) 1549 Kbps (inc. overheads)
Upstream 178 Kbps (22.3 KB/sec) 192 Kbps (inc. overheads)
and 5 mins ago slight upstream slowdown
Downstream 223 Kbps (27.9 KB/sec) 240 Kbps (inc. overheads)
Upstream 165 Kbps (20.6 KB/sec) 178 Kbps (inc. overheads)
other speedtest's vary but none are faster then half a mbit.
some pings from 11am to my gateway
Reply from 82.21.24.254: bytes=32 time=86ms TTL=255
Reply from 82.21.24.254: bytes=32 time=44ms TTL=255
Reply from 82.21.24.254: bytes=32 time=11ms TTL=255
Reply from 82.21.24.254: bytes=32 time=61ms TTL=255
Reply from 82.21.24.254: bytes=32 time=54ms TTL=255
Reply from 82.21.24.254: bytes=32 time=35ms TTL=255
Reply from 82.21.24.254: bytes=32 time=8ms TTL=255
Reply from 82.21.24.254: bytes=32 time=26ms TTL=255
Reply from 82.21.24.254: bytes=32 time=29ms TTL=255
Reply from 82.21.24.254: bytes=32 time=14ms TTL=255
Reply from 82.21.24.254: bytes=32 time=81ms TTL=255
Reply from 82.21.24.254: bytes=32 time=28ms TTL=255
Reply from 82.21.24.254: bytes=32 time=14ms TTL=255
Reply from 82.21.24.254: bytes=32 time=16ms TTL=255
Reply from 82.21.24.254: bytes=32 time=24ms TTL=255
Reply from 82.21.24.254: bytes=32 time=9ms TTL=255
Reply from 82.21.24.254: bytes=32 time=12ms TTL=255
Reply from 82.21.24.254: bytes=32 time=86ms TTL=255
Reply from 82.21.24.254: bytes=32 time=65ms TTL=255
Reply from 82.21.24.254: bytes=32 time=64ms TTL=255
Reply from 82.21.24.254: bytes=32 time=73ms TTL=255
Reply from 82.21.24.254: bytes=32 time=64ms TTL=255
Reply from 82.21.24.254: bytes=32 time=9ms TTL=255
Reply from 82.21.24.254: bytes=32 time=33ms TTL=255
Reply from 82.21.24.254: bytes=32 time=9ms TTL=255
Reply from 82.21.24.254: bytes=32 time=8ms TTL=255
Reply from 82.21.24.254: bytes=32 time=107ms TTL=255
and few mins ago
Reply from 82.21.24.254: bytes=32 time=85ms TTL=255
Reply from 82.21.24.254: bytes=32 time=128ms TTL=255
Reply from 82.21.24.254: bytes=32 time=134ms TTL=255
Reply from 82.21.24.254: bytes=32 time=112ms TTL=255
Reply from 82.21.24.254: bytes=32 time=133ms TTL=255
Reply from 82.21.24.254: bytes=32 time=135ms TTL=255
Reply from 82.21.24.254: bytes=32 time=24ms TTL=255
Reply from 82.21.24.254: bytes=32 time=10ms TTL=255
Reply from 82.21.24.254: bytes=32 time=32ms TTL=255
Reply from 82.21.24.254: bytes=32 time=116ms TTL=255
I dont know of anyone else who has a service as poor as this I am seriously considering asking for a discount until it is resolved but do ntl have a minimum performance level they expect to hit or will they just tell me sorry its contended you have to live with it.
this is combined with the poorer transit routing I have noticed to my ip range, I fail to see why I should pay the same for a much worse service then others on ntl.
|