High packloss, dropped connection & Extreme Latency - Fri/Sat/Sunday nights

[BorJJ]

Hi,

In the NR3 area of Norwich and over the last few weeks my connecton has been getting progressivly worse... culminating in todays performance where I can't even use it for surfing...

It's taken multiple tries to get on to this webiste with conintual times outs.. (even google)...

Some info

http://www.pingtest.net/result/28585456.png

My upload is faster than my download apparently...

http://www.speedtest.net/result/1039482583.png

Not just the speedtest.. prevously I could get 5.2meg from nvidia.com.. now I'm only getting 20k!

Which is nice.

Average of 25% packet loss to BBC.CO.UK

C:\Users\Robj>ping -t bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Request timed out.
Reply from 212.58.224.138: bytes=32 time=153ms TTL=119
Reply from 212.58.224.138: bytes=32 time=45ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=209ms TTL=119
Reply from 212.58.224.138: bytes=32 time=171ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=240ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=52ms TTL=119
Reply from 212.58.224.138: bytes=32 time=31ms TTL=119
Reply from 212.58.224.138: bytes=32 time=61ms TTL=119
Reply from 212.58.224.138: bytes=32 time=232ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=23ms TTL=119
Reply from 212.58.224.138: bytes=32 time=128ms TTL=119
Reply from 212.58.224.138: bytes=32 time=218ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=28ms TTL=119
Reply from 212.58.224.138: bytes=32 time=167ms TTL=119
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.224.138: bytes=32 time=37ms TTL=119
Reply from 212.58.224.138: bytes=32 time=233ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=233ms TTL=119
Reply from 212.58.224.138: bytes=32 time=29ms TTL=119

[BorJJ]

It's taken me 15 minutes to be able to post a reply with additonal info.

At least this is the first time I've had chronic problems with the connection.. OH WAIT.

Cable Modem Downstream DS-1 DS-2 DS-3 DS-4 Frequency 298750000 306750000 314750000 N/A Lock Status (QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y N/N/N Channel Id 33 34 35 N/A Modulation 256QAM 256QAM 256QAM N/A Symbol Rate (Msym/sec) 6.952 6.952 6.952 N/A Interleave Depth I=12 J=17 I=12 J=17 I=12 J=17 N/A Power Level (dBmV) 5.30 4.64 4.35 N/A RxMER (dB) 38.61 38.26 38.61 N/A Correctable Codewords 541 241 100 N/A Uncorrectable Codewords 1018 963 316 N/A Cable Modem Upstream US-1 US-2 US-3 US-4 Channel Type 1.0 N/A N/A N/A Channel ID 2 N/A N/A N/A Frequency (Hz) 46200000 N/A N/A N/A Ranging Status Success N/A N/A N/A Modulation QPSK N/A N/A N/A Symbol Rate (KSym/sec) 2560 N/A N/A N/A Mini-Slot Size 2 N/A N/A N/A Power Level (dBmV) 34.00 N/A N/A N/A T1 Timeouts 0 0 0 0 T2 Timeouts 0 0 0 0 T3 Timeouts 120 0 0 0 T4 Timeouts 4 0 0 0

[BorJJ]

Cable Modem Event Log First Time Last Time Priority Description Fri Nov 5 14:38:07 2010 Fri Nov 5 14:38:07 2010 Warning (5) B-INIT-RNG Failure - Retries exceeded Fri Nov 5 14:38:09 2010 Fri Nov 5 14:38:30 2010 Critical (3) No Ranging Response received - T3 time-out Fri Nov 5 14:38:44 2010 Fri Nov 5 14:38:44 2010 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Sun Nov 7 12:55:50 2010 Sun Nov 14 12:56:01 2010 Notice (6) DHCP Renew - lease parameters tftp file-V668732788139190d.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Mon Nov 15 23:59:52 2010 Mon Nov 15 23:59:53 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:00:15 2010 Tue Nov 16 00:00:15 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Tue Nov 16 00:00:41 2010 Tue Nov 16 00:00:41 2010 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:02:29 2010 Tue Nov 16 00:02:30 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:02:41 2010 Tue Nov 16 00:02:41 2010 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:02:44 2010 Tue Nov 16 00:02:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Tue Nov 16 00:03:01 2010 Tue Nov 16 00:03:01 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:03:01 2010 Tue Nov 16 00:03:01 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:03:14 2010 Tue Nov 16 00:03:14 2010 Critical (3) No Ranging Response received - T3 time-out Tue Nov 16 00:05:21 2010 Tue Nov 16 00:05:21 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:05:36 2010 Tue Nov 16 00:05:36 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:05:36 2010 Tue Nov 16 00:05:36 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:07:57 2010 Tue Nov 16 00:07:57 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:08:12 2010 Tue Nov 16 00:08:12 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:08:12 2010 Tue Nov 16 00:08:36 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:08:36 2010 Tue Nov 16 00:08:36 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:08:50 2010 Tue Nov 16 00:08:53 2010 Critical (3) No Ranging Response received - T3 time-out Tue Nov 16 00:11:01 2010 Tue Nov 16 00:11:01 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:11:16 2010 Tue Nov 16 00:11:16 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:11:17 2010 Tue Nov 16 00:11:40 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:11:41 2010 Tue Nov 16 00:11:41 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:14:03 2010 Tue Nov 16 00:14:03 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:14:18 2010 Tue Nov 16 00:14:18 2010 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:14:18 2010 Tue Nov 16 00:14:18 2010 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:15:04 2010 Tue Nov 16 00:15:59 2010 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:20:42 2010 Tue Nov 16 00:20:42 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Tue Nov 16 00:21:47 2010 Tue Nov 16 00:21:47 2010 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Tue Nov 16 00:36:15 2010 Tue Nov 16 00:36:15 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Tue Nov 16 00:36:31 2010 Tue Nov 16 00:37:47 2010 Critical (3) No Ranging Response received - T3 time-out Tue Nov 16 00:37:59 2010 Tue Nov 16 00:37:59 2010 Warning (5) B-INIT-RNG Failure - Retries exceeded Tue Nov 16 00:38:01 2010 Tue Nov 16 00:38:20 2010 Critical (3) No Ranging Response received - T3 time-out Tue Nov 16 00:38:21 2010 Tue Nov 16 00:38:21 2010 Critical (3) Ranging Request Retries exhausted Tue Nov 16 00:38:21 2010 Tue Nov 16 00:38:21 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted Tue Nov 16 00:38:34 2010 Tue Nov 16 00:39:07 2010 Critical (3) No Ranging Response received - T3 time-out Tue Nov 16 00:39:28 2010 Tue Nov 16 00:39:28 2010 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; Thu Nov 18 18:47:49 2010 Thu Nov 18 18:47:49 2010 Notice (6) DHCP Renew - lease parameters tftp file-V668732788139190d.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[BorJJ]

Ok how do I post the info in a useable format please?

[simonb1975]

hi i am in the nr5 norwich area and get high ping packet loss and slow speeds under 10 meg when i pay for 50meg for 7 weeks now had it with vm ripping me off and going to bt

[Chris666]

Hi ya im also in norwich (NR7) and also having major problems with the internet.

My trouble though is with upload speeds and latency. (0.05 mb tonight)

Dont even ask me about ping tests as i have had results of over 1k+ ms at some times of the evenings.

I was given fault reference f001386316.

There is obviously a major problem in NORWICH now and should be made priority now.

So that means there is at least 2 fault reference codes in norwich now if not more!!!!

[Paul_B]

Hi BorJJ,

 The utilisation did peak on the 21st and 22nd in the evening for your self. This has gone down to a more acceptable level. We shall continue to monitor this and if it becomes more consistent or increases we shall pass to our network team to investigate.