Virgin Media Community

[Nick_Key]

Hello, I recently upgraded from your 100mb broadband (which always gave close to 100mb on speedtest.net) to M200. It was good for a short period but I now only get between 40mb and 70mb.  

Ive jumped through the hoops here: https://community.virginmedia.com/t5/Digital-life/Broadband-Speed-Check/ba-p/3459473 to no avail. I have copied the logs from the router but they exceed the 20,000 character max post size!

Many thanks,

[jpeg1]

What device/s are you measuring the speed with?  Are they connected to the Hub with a good quality ethernet cable? 

[Nick_Key]

Hi jpeg1, 

Good point - i should have said. Connection being measured on a laptop, connected via decent ethernet cables.

The same main device has been used all the way though, measuring ~100mb on my old deal, then ~200mb, but now only 40-70mb. No wiring or hardware changes have been made. But its the story with other devices in the house. I assumed it was a bad day / fault in the area but its been like this for a couple of weeks now. 

[jbrennand]

Try changing to a new Cat6 ethernet cable. They can and do "fail" and drop back to 10/100 speeds. Also look in the laptop settings and chech that the connection speed has not dropped from 1GB to 100Mbps. Check the drivers are up to date.

Then can you test this way.
_____________________________

As you expect >100Mbps then connect a 1GB enabled computer/laptop, with up to date drivers, via a NEW and working Cat5e/6a ethernet cable, directly to the Hub which you have put into “modem mode”

(https://www.virginmedia.com/help/virgin-media-hub-modem-mode ).

This ensures that NO other devices can be connected

Test speeds at https://speedtest.samknows.com/ - try on 2 different browsers.

If they are still low – boot your device into Windows safe+networking mode - to disable any potentially interfering software - and try again.

There are many posts on here (I have a list of ~30!) where QoS software, unknown/flaky software, old network card drivers, corrupted browsers, bad cables or other connected devices are limiting speeds on tests.

Report back what that gets.

[Andrew-G]

Break the hub status data into three separate posts for Downstream, Upstream and Network log (and if need be, post the network log into two).

There's no harm trying a new ethernet cable, but when that is the problem then normally we see the speed sitting at 85-95 Mbps, as a dodgy cable normally reverts to 100 Mbps protocol, and after the removal of the TCP/IP overheads 94 Mbps is the result.  Have another go posting the data and we can comment for you.

[Nick_Key]

Thank you, will try another cat6 cable and let you know. 

Logs: 

Downstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	234750000	9	38	256 qam	13
2	138750000	11.6	38	256 qam	1
3	146750000	11.5	40	256 qam	2
4	154750000	11.5	40	256 qam	3
5	162750000	11	40	256 qam	4
6	170750000	11	40	256 qam	5
7	178750000	10.9	40	256 qam	6
8	186750000	10.5	38	256 qam	7
9	194750000	10.1	38	256 qam	8
10	202750000	9.9	38	256 qam	9
11	210750000	9.5	38	256 qam	10
12	218750000	9.3	38	256 qam	11
13	226750000	9.1	38	256 qam	12
14	242750000	8.8	38	256 qam	14
15	250750000	8.5	38	256 qam	15
16	258750000	8.5	38	256 qam	16
17	266750000	9	38	256 qam	17
18	274750000	9	38	256 qam	18
19	282750000	9.4	38	256 qam	19
20	290750000	9.4	40	256 qam	20
21	298750000	9.5	38	256 qam	21
22	306750000	9.5	40	256 qam	22
23	314750000	9.8	40	256 qam	23
24	322750000	9.6	40	256 qam	24

Downstream bonded channels

Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	38.9	18930	10848
2	Locked	38.9	13479	16122
3	Locked	40.3	10549	18923
4	Locked	40.3	7599	21859
5	Locked	40.3	4629	24757
6	Locked	40.3	3006	26475
7	Locked	40.3	4401	24972
8	Locked	38.6	4265	25223
9	Locked	38.9	6476	22825
10	Locked	38.9	10103	18962
11	Locked	38.9	10861	18200
12	Locked	38.9	16183	14493
13	Locked	38.9	18127	12408
14	Locked	38.9	19271	10760
15	Locked	38.6	19337	11490
16	Locked	38.9	19251	9846
17	Locked	38.6	17498	8614
18	Locked	38.6	16168	10419
19	Locked	38.9	14517	4361
20	Locked	40.3	13987	10720
21	Locked	38.9	12886	3419
22	Locked	40.3	9700	4490
23	Locked	40.3	7954	4730
24	Locked	40.3	7150	4909

[Nick_Key]

Upstream bonded channels

Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	60300000	39	5120	64 qam	1
2	39400000	37.3	5120	64 qam	4
3	46200000	37.5	5120	64 qam	3
4	53700000	38.8	5120	64 qam	2

Upstream bonded channels

Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	ATDMA	0	0	10	0
2	ATDMA	0	0	12	0
3	ATDMA	0	0	13	0
4	ATDMA	0	0	17	0

[Nick_Key]

Network Log

Time	Priority	Description
22/03/2022 09:35:45	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 22:49:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 17:46:0	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 17:46:0	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:35:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:35:10	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:01:33	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:01:33	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:24:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:24:9	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:30	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:9	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:49	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:29	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:29	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:20:29	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:20:29	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[muffintastic]

---

@Nick_Key wrote:

Network Log

Time	Priority	Description
22/03/2022 09:35:45	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 22:49:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 17:46:0	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/03/2022 17:46:0	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:35:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:35:10	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:01:33	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2022 08:01:33	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:24:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:24:9	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:30	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:23:9	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:49	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:29	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:21:29	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:20:29	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/03/2022 08:20:29	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

---

Have you tried running a service check https://www.virginmedia.com/help/service-status If it says fine then try clicking 'Broadband' then a drop down menu will appear then press 'Test your hub' if that comes back fine then try hard resetting the hub and starting from scratch, this is kind of a last resort measure.

[Andrew-G]

Amongst several other problems, your downstream power levels are too high.  I've marked for staff to take a look and advise - probably needs a technician visit.