Cable slowed to a crawl at peak times, like clockwork
 

Hey,

I'm in the SW20 region of London, and every night from around 6pm to about 10pm the internet slows to a complete crawl, download speeds go from 46-50mb to 0.5-2mb. There also appears to be packet loss, games and steaming media don't work and the internet cuts out if anything too intensive is going on.

This seems to happen around the same time every night like clockwork, I was wondering if this could be anything on my side, or some kind of traffic limiting, or even something I could fix myself rather than simply overcrowding, overuse or aforementioned Virgin limiting my speeds?

Thanks for any and all responses,

Mack

Re: Cable slowed to a crawl at peak times, like clockwork
 

There's nothing to go on in your information to glean what you could do yourself in the circumstances. Frankly it needs to be reported with some before and after evidence because 99.5% sure it's congestion or a circuit fault that hits you during a congested period.

We can try to part-diagnose this for you if you provide us with stats just before and again when when things are bad. Quite often we can validly suggest a cause for an unstable service based on the data you provide as listed below.


1/
Your modem stats (to include Downstream, Upstream, Operational Config & event log). This is achieved by entering http://192.168.100.1 in your browser and hitting the Login link, supplying credentials "root" and "root". You then click on each of the menu items I've listed and copy the results into your next post (e.g. by cutting & pasting into Notepad.exe and then copying the lot into the post).
IMPORTANT: REMOVE YOUR IP ADDRESS FROM ANY INFORMATION (You can leave 192.168.xx.xx in).


2/
A speed test preferably using http://www.virginmedia.com/testmyspeed/manual.php.


3/
Just before modem stats, please do PATHPING www.bbc.co.uk. Pathping takes a few minutes to run and tells us where congestion might be occurring. If you type pathping www.bbc.co.uk > c:\fred.txt at the windows command prompt, then you can use notepad to extract and paste all the information in c:\fred.txt or another location of your choice.

The result of the above would be advice on what to tell the support people when it's called in.

Cheers

Re: Cable slowed to a crawl at peak times, like clockwork
 

1/

DOWNSTREAM

Frequency 315000000 299000000 307000000 N/A
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y N/N/N
Channel Id 53 51 52 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) 6.34 6.24 5.97 N/A
RxMER
(dB) 36.17 35.97 35.42 N/A
Correctable
Codewords 3598807 765477 173223102 N/A
Uncorrectable
Codewords 284 297 294 N/A

UPSTREAM

Channel Type 1.0 N/A N/A N/A
Channel ID 2 N/A N/A N/A
Frequency
(Hz) 25800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM 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) 41.75 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 17 0 0 0
T4 Timeouts 0 0 0 0

OPERATIONAL CONFIG.

Cable Modem Operation Configuration
General Configuration
Network Access : Allowed
Maximum Number of CPEs : 1
Baseline Privacy : Enabled
DOCSIS Mode : DOCSIS 3.0
Config File : yewrkldJKDHSUBsgvca6
Primary Downstream Service Flow
SFID : 2031
Max Traffic Rate : 53000000 bps
Max Traffic Burst : 3044 bytes
Min Traffic Rate : 0 bps
Primary Upstream Service Flow
SFID : 2030
Max Traffic Rate : 1750000 bps
Max Traffic Burst : 3044 bytes
Min Traffic Rate : 0 bps
Max Concatenated Burst : 1522 bytes
Scheduling Type : Best Effort

EVENT LOG

Thu Jan 28 00:51:22 2010 Thu Jan 28 00:51:22 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:53:33 2010 Thu Jan 28 00:53:33 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:53:40 2010 Thu Jan 28 00:53:40 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:53:53 2010 Thu Jan 28 00:53:53 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=00:21:d8:d1:b9:b7;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:56:00 2010 Thu Jan 28 00:56:00 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:56:07 2010 Thu Jan 28 00:56:07 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:56:20 2010 Thu Jan 28 00:56:20 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:58:29 2010 Thu Jan 28 00:58:29 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:58:36 2010 Thu Jan 28 00:58:36 2010 Warning (5) MDD message timeout;CM-removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 00:58:49 2010 Thu Jan 28 00:58:49 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:00:55 2010 Thu Jan 28 01:00:55 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:01:02 2010 Thu Jan 28 01:01:02 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:01:15 2010 Thu Jan 28 01:01:15 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:03:22 2010 Thu Jan 28 01:03:22 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:03:29 2010 Thu Jan 28 01:03:29 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:03:43 2010 Thu Jan 28 01:03:43 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:05:52 2010 Thu Jan 28 01:05:52 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:06:00 2010 Thu Jan 28 01:06:00 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:06:12 2010 Thu Jan 28 01:06:12 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:08:23 2010 Thu Jan 28 01:08:23 2010 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:08:31 2010 Thu Jan 28 01:08:31 2010 Warning (5) MDD message timeout;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:08:43 2010 Thu Jan 28 01:09:16 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:09:23 2010 Thu Jan 28 01:09:23 2010 Critical (3) Registration RSP rejected unspecified reason;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:09:23 2010 Thu Jan 28 01:09:23 2010 Critical (3) Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:17:45;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:09:23 2010 Thu Jan 28 01:09:23 2010 Error (4) T6 Timeout and retries exceeded;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 01:09:23 2010 Thu Jan 28 01:09:23 2010 Critical (3) REG RSP not received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:05:23 2010 Thu Jan 28 19:05:23 2010 Notice (6) Received REG-RSP while in REG-HOLD1 state;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:05:44 2010 Thu Jan 28 19:05:44 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed5;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:06:05 2010 Thu Jan 28 19:06:05 2010 Notice (6) Received REG-RSP while in REG-HOLD1 state;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:06:21 2010 Thu Jan 28 19:06:21 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:06:38 2010 Thu Jan 28 19:06:38 2010 Notice (6) Received REG-RSP while in REG-HOLD1 state;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:06:59 2010 Thu Jan 28 19:06:59 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 28 19:07:14 2010 Thu Jan 28 19:07:14 2010 Warning (5) ToD request sent - No Response received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 29 02:38:17 2010 Fri Jan 29 02:38:31 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 29 02:38:32 2010 Fri Jan 29 02:38:32 2010 Critical (3) Ranging Request Retries exausted;CM-MAC=removed;CMTS-MAC=00:21:d8:d1:b6:9d;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 29 02:38:32 2010 Fri Jan 29 02:38:32 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:68:f0:17:45;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;


2/ https://www.cableforum.co.uk/images/local/2010/01/8.png

3/ Tracing route to bbc.co.uk [212.58.224.138]

over a maximum of 30 hops:

0 mack [192.168.1.2]

1 192.168.1.1

2 10.89.168.1

3 nmal-geam-1b-ge14.network.virginmedia.net [81.96.225.137]

4 osr02croy-pc112.network.virginmedia.net [62.30.242.53]

5 pop-bb-b-ae2-0.network.virginmedia.net [195.182.178.86]

6 gfd-bb-a-so-010-0.network.virginmedia.net [213.105.172.137]

7 gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]

8 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]

9 212.58.239.249

10 212.58.238.149

11 virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Thanks alot for your reply, I hope this is in the correct format, and if it is i'll do it again tonight when the internet begins to slow to a halt again.

Thanks, Mack

Re: Cable slowed to a crawl at peak times, like clockwork
 

Your levels are fine, you speedtest is fine, not sure about trace route but doesn't look wrong to me, you are most likely going to find its congestion which will need to report it and then VM will have sort it out just don't expect a quick fix congestion related faults normally take longer to sort out, due to all the planning,part,funds and more much to take in to account.

Re: Cable slowed to a crawl at peak times, like clockwork
 

Thanks. When you do it again tonight, please use PATHPING rather tham Tracert.

Anyway, it looks like the second of my diagnosis points would apply. To be confirmed this evening. I suspect there's a circuit problem that kicks in during peak load times. I'll explain.

There are a very large number of packets arriving at the cable modem with errors that are correctable by the Reed-Solomon mechanism.

Correctable
Codewords 3598807 765477 173223102 N/A
Uncorrectable
Codewords 284 297 294 N/A

Some of these are uncorrectable. It may be that this has given rise to the T6 message which means that the CM has not been able to register and is restarting the registration process.

Other than that, you SNR and other modem stats are fine.

The T3 errors occur at non-peak times as well. The wisdom is that noise on the upstream channel is the cause of T3 timeouts. It will be worse at peak times when there is contention for a time slot on the upstream channel.

Without more ado (but it would be instructive to see your later figures), you could post your modem stats and event log on the support newsgroup. They'll check your circuit and post back their informed opinion as to what's going on. Point out to them the T3 timeouts and the Correctable Codewords.

If you're on Vista or Windows 7, you would use Windows Live Mail (a standard part of your system). To get on the VM Newsgroup you need to be operating through the VM broadband system.

In Windows Live Mail, you'd click the "Newsgroups" link at the bottom of the screen and then Tools/Accounts then Add/Newsgroup Account.

Give your Display Name (like rsdx), your e-mail address (optional or you can make one up!) then your server address for the newsgroup which is "news.virginmedia.com".

You'll then be able (via the Newsgroups menu item) to select the Virgin media icon on the left of a search panel, click on "All" and wait a few minutes till it's finished listing thousands of newsgroups.

Scroll down to "Virginmedia.support.broadband.cable" and double click it.

And you're there. You can post your stuff including any evidence you've collected.

HTH.

PS EDIT: Now you're forked between Broadbandking's advice and mine!

Re: Cable slowed to a crawl at peak times, like clockwork
 

As a quick aside, OP please could you reboot your cable modem - the nasty errors are all during traditional maintenance windows and could be a result of planned work. It'd be good to get these gone and get a clean slate.

Re: Cable slowed to a crawl at peak times, like clockwork
 

Right, yesterday night it was (Weirdly?) fine, but tonight at this time (late at night - again, out of the ordinary clockwork cycle) it's giving me large packet loss in all streaming applications (iplayer, vent, games)

1/

DOWNSTREAM

Frequency 315000000 299000000 307000000 N/A
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y N/N/N
Channel Id 53 51 52 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) 7.59 7.51 7.22 N/A
RxMER
(dB) 36.61 36.17 35.97 N/A
Correctable
Codewords 8641894 2604465 167273580 N/A
Uncorrectable
Codewords 294 293 284 N/A

UPSTREAM

Channel Type 1.0 N/A N/A N/A
Channel ID 2 N/A N/A N/A
Frequency
(Hz) 25800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM 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) 41.75 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 33 0 0 0
T4 Timeouts 0 0 0 0

OPERATIONAL CONFIG.

General Configuration
Network Access : Allowed
Maximum Number of CPEs : 1
Baseline Privacy : Enabled
DOCSIS Mode : DOCSIS 3.0
Config File : dsfd;kfoA,.iyewrkldJ
Primary Downstream Service Flow
SFID : 2031
Max Traffic Rate : 53000000 bps
Max Traffic Burst : 3044 bytes
Min Traffic Rate : 0 bps
Primary Upstream Service Flow
SFID : 2030
Max Traffic Rate : 1750000 bps
Max Traffic Burst : 3044 bytes
Min Traffic Rate : 0 bps
Max Concatenated Burst : 1522 bytes
Scheduling Type : Best Effort

EVENT LOG (cleared since last post)

Sat Jan 30 14:23:52 2010 Sat Jan 30 14:24:06 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 30 14:24:07 2010 Sat Jan 30 14:24:07 2010 Critical (3) Ranging Request Retries exausted;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 30 14:24:07 2010 Sat Jan 30 14:24:07 2010 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=removed;CMTS-MAC=removed;CM-QOS=1.1;CM-VER=3.0;


2/ https://www.cableforum.co.uk/images/local/2010/01/3.png

3/ Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mackzj>pathping www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
0 mack [192.168.1.2]
1 192.168.1.1
2 10.89.168.1
3 nmal-geam-1b-ge14.network.virginmedia.net [81.96.225.137]
4 osr02croy-pc112.network.virginmedia.net [62.30.242.53]
5 pop-bb-b-ae2-0.network.virginmedia.net [195.182.178.86]
6 gfd-bb-a-so-010-0.network.virginmedia.net [213.105.172.137]
7 gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]
8 * redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
9 212.58.239.249
10 212.58.238.133
11 te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
12 www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Computing statistics for 300 seconds...

I really appreciate your replies on this, it's weird that the downoad/upload seems pretty good, but i'm still getting this huge packet loss. I've added another test I think might indicate there is a problem below, again, I appreciate your help guys.

4/ http://www.pingtest.net/result/9265925.png

Re: Cable slowed to a crawl at peak times, like clockwork
 

You didn't let the pathping run through to the end. So the ping packet information is missing. Pingtest.net is, unfortunately useless for our purpose here.

Anyway, as I said in post #5, the T3 timeouts and codewords issue needs to be reported. If gaming pings are giving problems, it's indicative of an upstream issue as supported by the T3 timeouts.

Please post the FIRST modem stats and event log to the support newsgrroup who'll analyse your circuit and advise next actions.

If you're on Vista or Windows 7, you would use Windows Live Mail (a standard part of your system). To get on the VM Newsgroup you need to be operating through the VM broadband system.

In Windows Live Mail, you'd click the "Newsgroups" link at the bottom of the screen and then Tools/Accounts then Add/Newsgroup Account.

Give your Display Name (like rsdx), your e-mail address then your server address for the newsgroup which is "news.virginmedia.com".

You'll then be able (via the Newsgroups menu item) to select the Virgin media icon on the left of a search panel, click on "All" and wait a few minutes till it's finished listing thousands of newsgroups.

Scroll down to "Virginmedia.support.broadband.cable" and double click it.


And you're there. You can post your stuff including any evidence you've collected.

Re: Cable slowed to a crawl at peak times, like clockwork
 

Oops, you're dead right, posting it now for the sake of curiosity.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mackzj>pathping www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
0 mack [192.168.1.2]
1 192.168.1.1
2 10.89.168.1
3 nmal-geam-1b-ge14.network.virginmedia.net [81.96.225.137]
4 osr02croy-pc112.network.virginmedia.net [62.30.242.53]
5 pop-bb-b-ae2-0.network.virginmedia.net [195.182.178.86]
6 gfd-bb-a-so-010-0.network.virginmedia.net [213.105.172.137]
7 gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]
8 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
9 212.58.239.249
10 212.58.238.133
11 te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
12 www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 mack [192.168.1.2]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.89.168.1
0/ 100 = 0% |
3 38ms 0/ 100 = 0% 0/ 100 = 0% nmal-geam-1b-ge14.network.virginme
dia.net [81.96.225.137]
0/ 100 = 0% |
4 38ms 0/ 100 = 0% 0/ 100 = 0% osr02croy-pc112.network.virginmedi
a.net [62.30.242.53]
0/ 100 = 0% |
5 41ms 0/ 100 = 0% 0/ 100 = 0% pop-bb-b-ae2-0.network.virginmedia
.net [195.182.178.86]
0/ 100 = 0% |
6 37ms 0/ 100 = 0% 0/ 100 = 0% gfd-bb-a-so-010-0.network.virginme
dia.net [213.105.172.137]
0/ 100 = 0% |
7 40ms 2/ 100 = 2% 2/ 100 = 2% gfd-bb-b-ae0-0.network.virginmedia
.net [213.105.172.6]
0/ 100 = 0% |
8 36ms 1/ 100 = 1% 1/ 100 = 1% redb-ic-1-as0-0.network.virginmedi
a.net [62.253.185.78]
0/ 100 = 0% |
9 48ms 0/ 100 = 0% 0/ 100 = 0% 212.58.239.249
0/ 100 = 0% |
10 46ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.133
0/ 100 = 0% |
11 47ms 0/ 100 = 0% 0/ 100 = 0% te12-1.hsw0.cwwtf.bbc.co.uk [212.5
8.239.222]
0/ 100 = 0% |
12 39ms 0/ 100 = 0% 0/ 100 = 0% www-vip.cwwtf.bbc.co.uk [212.58.25
3.67]

Trace complete.

C:\Documents and Settings\Mackzj>

Thanks for your advice, will get onto the newsgroups now.

-Mack

Re: Cable slowed to a crawl at peak times, like clockwork
 

The Pathping isn't good (I've seen much worse though) - the time taken to get on the network. But the event log (first) and the codewords situation is what the 2nd line support people should focus on.

Keep us advised.

Cheers

Re: Cable slowed to a crawl at peak times, like clockwork
 

Hey, just checking in;

"I have identified a local upstream issue causing your slow speeds that I
have passed to our network team to resolve. We're sorry for any
inconvenience caused."

that's the response I've gotten, and isn't it just great? guess it's something they can resolve!

Thanks again,

Mack

Re: Cable slowed to a crawl at peak times, like clockwork
 

Well, new reply, they say it'll take 6-8 weeks to fix but right now i'm getting around 10% packet loss, can't talk on vent or play any games.

I'm wondering if going with another provider temporarily will be an instant fix? Don't really fancy paying for 8 weeks and not being able to use it.