Slow Speeds WA11

[NeilB]

LO Everybody

Wondering if anybody else is having probelms in the WA11 area its been going on for months but this week has been the worst ever they sent me a new modem last week that has not fixed the issue but now im being told its a network issue thats being worked on with no date of when it will be fixed.

My UBR xx-xxx-xx-xxx.cable.ubr10.know.blueyonder.co.uk

there is no make on the modem all i can find on the bottom is trade name ambit?

my stats from my modem

Cable Modem Status
Item Status Comments
Acquire a Downstream Channel 331000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational

Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 0
Downstream Frequency : 331000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : -4.1 dBmV
Downstream SNR : 35.4 dB

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 3
Upstream Frequency : 23000000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 1280 Ksym/sec
Upstream transmit Power Level : 32.0 dBmV
Upstream Mini-Slot Size : 4

Thanks.

Hi NeilB and welcome to the forum.
A new modem would never have helped if its a network issue.

Were you given any more info as to what the network problem was?

[NeilB]

I have been told that the network is over populated and also that its due to work installing the new 50mb??

---------- Post added at 21:15 ---------- Previous post was at 21:10 ----------

Its is getting worse everyday normally i dont loose packets.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Neil>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=40ms TTL=119
Reply from 212.58.224.138: bytes=32 time=40ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=50ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 50ms, Average = 43ms

C:\Users\Neil>

[NeilB]

Surley others are having these problems as well or is just me?

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Neil>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=73ms TTL=119
Reply from 212.58.224.138: bytes=32 time=84ms TTL=119
Reply from 212.58.224.138: bytes=32 time=83ms TTL=119
Reply from 212.58.224.138: bytes=32 time=91ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 91ms, Average = 82ms

C:\Users\Neil>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=49ms TTL=119
Reply from 212.58.224.138: bytes=32 time=56ms TTL=119
Reply from 212.58.224.138: bytes=32 time=57ms TTL=119
Reply from 212.58.224.138: bytes=32 time=66ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 66ms, Average = 57ms

C:\Users\Neil>

From the results of your pings I'd be more inclined to say it was FEC
http://en.wikipedia.org/wiki/Forward_error_correction