I had an engineer come out today. He changed all of my cables and connectors, as I did had some really bad readings. He fixed those and put an attenuator on the box at the front of my house as he said I was having too high of a signal coming through. He left about 15:40ishI was told my downstream should read about 7's where before it was on 11/12's.It was okay for about 30-40 mins and now it seems even worse than before. I am a gamer, I am unable to enjoy anything atm, I pay for a good connection and speed. This is honestly the worst service I have ever had. If everything is okay at my property what the hell is the cause of this? Can I get some help?https://www.thinkbroadband.com/broadband/monitoring/quality/share/e18e4e2305216a9f9889895ab93d8ffb57a01144-24-11-2023 3.0 Downstream channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 13780000006.242QAM 2563121380000008.341QAM 256131460000007.941QAM 256241540000007.941QAM 256351620000007.941QAM 256461700000007.741QAM 256571780000007.741QAM 256681860000007.741QAM 256791940000007.941QAM 256810202000000842QAM 256911210000000842QAM 25610122180000007.942QAM 25611132260000007.742QAM 25612142340000007.642QAM 25613152420000007.342QAM 25614162500000007.142QAM 25615172580000007.142QAM 2561618266000000742QAM 25617192740000007.142QAM 25618202820000007.142QAM 2561921290000000742QAM 25620222980000007.142QAM 25621233060000007.242QAM 25622243140000007.242QAM 25623253220000007.342QAM 2562426330000000742QAM 25625273380000006.742QAM 25626283460000006.542QAM 25627293540000006.442QAM 25628303620000006.242QAM 25629313700000006.342QAM 256303.0 Downstream channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1Locked422146831393022Locked415842848270973Locked413752217243934Locked41932991280585Locked413072303534386Locked412511803197827Locked413631163116328Locked41716861014149Locked4110304113309110Locked4251197938977711Locked4225192722701912Locked4252722935112313Locked4221786418039214Locked4253670132324615Locked4255869632538816Locked4221329319130817Locked4223351423221018Locked4217310923521819Locked4223106818060120Locked4252127630952621Locked4245707724601822Locked4252739524893523Locked4252442524721824Locked4249109526127625Locked4226513821368726Locked4224297323394127Locked4227483022254128Locked4246577228070129Locked4224136423671430Locked4224041422298731Locked421878871753033.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 159924K1800QAM 409611283.1 Downstream channelsChannel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile) 159Locked436.255495986937 3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 046200000415120QAM 64113940000040.55120QAM 642232600000405120QAM 643353700000415120QAM 6443.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0ATDMA00001ATDMA00002ATDMA00003ATDMA0000 Network LogTime Priority Description 24-11-2023 16:00:14warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 16:00:13criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:49:11noticeREGISTRATION COMPLETE - Waiting for Operational status24-11-2023 15:49:05warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:48:52warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:48:50noticeHonoring MDD; IP provisioning mode = IPv424-11-2023 15:43:57criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:53warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:53criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:33criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:33criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:13criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:43:13criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:42:54criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:42:53criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:42:15warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:42:15criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:42:12criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:40:34noticeREGISTRATION COMPLETE - Waiting for Operational status24-11-2023 15:40:28warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:40:15warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:40:13noticeHonoring MDD; IP provisioning mode = IPv424-11-2023 15:40:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:40:00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:39:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:39:24warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:27warningRCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:27warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:22criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:21warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 15:38:18criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

No one said doing internet over Docsis would be perfect.You got some bad jitter plus if the engineer did change your cables and such why does your BQM not show this?Do you use HomePlug - Network Via Mains?

I used an old BQM I just realise. My mistake, that being said no Docsis internet won't always be perfect but since having everything tested and cables changed, why am I still experiencing the same issues I had before the engineer visit today? This should not be happing on a daily basis ALL day every few minutes... I'm not kidding, gaming for 12+ hours the past 2 days and I have issues EVERY couple minutes this is not normal and should not be happening, and did not happen previously.Nope, no homeplug, I am using ethernet directly into the hub.I have set up a new BQM so I shall post results tomorrow once it has updated, I'm certain it'll be all over the place.So any response from VM once that is done would be much appreciated, because I am honestly sick of it, there has to be a reason for these issues to still be happening.

Couple of things.. Switch the Hub off and unplug it from the mains supply for five minutes. Then switch the Hub back on and leave ~5 minutes When all done, check back in the settings and ensure that the RS error counts and any T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the PostRS and T3 ones) you have a problem.Secondly, what devices are plugged into the Hub on ethernet cables.? I ask because there have been several threads on here recently where similar BQM latency/packet loss problems were eventually pinned down to a dodgy piece of ethernet connected kit affecting the connection . Bad connectors on ethernet cables and faulty network switches being high on the list of culprits.What I advised was... if you run the BQM for 24h to get a picture of the issues (you have done this) - and then unplug all the ethernet cable connections from the Hub and just let it run - overnight is best - then in the morning look at the BQM and see if it has cleaned up. If it has - plug the devices back in one at a time for an hour or two until the problem reappears and that should indicate where to look for what is causing the issuesExamples.See message 21 in the first thread, 13 in the second and 5 in the thirdhttps://community.virginmedia.com/t5/Networking-and-WiFi/Internet-connection-dropping/td-p/4781287/page/3https://community.virginmedia.com/t5/Networking-and-WiFi/Intermittent-Connection/td-p/5069984/page/2https://community.virginmedia.com/t5/Speed/Issues-in-GU22-area/m-p/5400109#M307543

I have switched it off, unplugged it and waited like you suggested. I've checked all ethernet cables, from the outside they do not seem damaged. Made sure they are in in properly, including the power lead to the hub. Just to note I do not run modem mode, I do not have a third party router. I have PS5, PC and TV connected via ethernet.All PostRS back to 0 I will keep an eye on them all, I shall post new BQM once it's been 24 or more hours. Just as an example of what this is like whilst gaming.... this seems to happen literally every few minutes and it is constant, So I am positive that the BQM will come back with issues. As to the cause, given an engineer visit and him checking all cables to the house and changing where needed and new connectors. I am baffled as to what is going on.

Its not that hard to make anyone's BQM look bad with hubs and VM choose to not address it and yet they do other stuff like New Hub 5 Smart Security that we don't want!Test hub in modem mode to a PC or console

Forum Discussion

Aedrothica

On our wavelength

2 years ago

Network issues after engineer visit

I had an engineer come out today. He changed all of my cables and connectors, as I did had some really bad readings. He fixed those and put an attenuator on the box at the front of my house as he said I was having too high of a signal coming through. He left about 15:40ish

I was told my downstream should read about 7's where before it was on 11/12's.

It was okay for about 30-40 mins and now it seems even worse than before. I am a gamer, I am unable to enjoy anything atm, I pay for a good connection and speed. This is honestly the worst service I have ever had. If everything is okay at my property what the hell is the cause of this? Can I get some help?
https://www.thinkbroadband.com/broadband/monitoring/quality/share/e18e4e2305216a9f9889895ab93d8ffb57a01144-24-11-2023

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	378000000	6.2	42	QAM 256	31
2	138000000	8.3	41	QAM 256	1
3	146000000	7.9	41	QAM 256	2
4	154000000	7.9	41	QAM 256	3
5	162000000	7.9	41	QAM 256	4
6	170000000	7.7	41	QAM 256	5
7	178000000	7.7	41	QAM 256	6
8	186000000	7.7	41	QAM 256	7
9	194000000	7.9	41	QAM 256	8
10	202000000	8	42	QAM 256	9
11	210000000	8	42	QAM 256	10
12	218000000	7.9	42	QAM 256	11
13	226000000	7.7	42	QAM 256	12
14	234000000	7.6	42	QAM 256	13
15	242000000	7.3	42	QAM 256	14
16	250000000	7.1	42	QAM 256	15
17	258000000	7.1	42	QAM 256	16
18	266000000	7	42	QAM 256	17
19	274000000	7.1	42	QAM 256	18
20	282000000	7.1	42	QAM 256	19
21	290000000	7	42	QAM 256	20
22	298000000	7.1	42	QAM 256	21
23	306000000	7.2	42	QAM 256	22
24	314000000	7.2	42	QAM 256	23
25	322000000	7.3	42	QAM 256	24
26	330000000	7	42	QAM 256	25
27	338000000	6.7	42	QAM 256	26
28	346000000	6.5	42	QAM 256	27
29	354000000	6.4	42	QAM 256	28
30	362000000	6.2	42	QAM 256	29
31	370000000	6.3	42	QAM 256	30

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	42	214683	139302
2	Locked	41	584284	827097
3	Locked	41	375221	724393
4	Locked	41	93299	128058
5	Locked	41	307230	353438
6	Locked	41	251180	319782
7	Locked	41	363116	311632
8	Locked	41	71686	101414
9	Locked	41	103041	133091
10	Locked	42	511979	389777
11	Locked	42	251927	227019
12	Locked	42	527229	351123
13	Locked	42	217864	180392
14	Locked	42	536701	323246
15	Locked	42	558696	325388
16	Locked	42	213293	191308
17	Locked	42	233514	232210
18	Locked	42	173109	235218
19	Locked	42	231068	180601
20	Locked	42	521276	309526
21	Locked	42	457077	246018
22	Locked	42	527395	248935
23	Locked	42	524425	247218
24	Locked	42	491095	261276
25	Locked	42	265138	213687
26	Locked	42	242973	233941
27	Locked	42	274830	222541
28	Locked	42	465772	280701
29	Locked	42	241364	236714
30	Locked	42	240414	222987
31	Locked	42	187887	175303

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

1800

QAM 4096

1128

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

6.2

554959

86937

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	46200000	41	5120	QAM 64	1
1	39400000	40.5	5120	QAM 64	2
2	32600000	40	5120	QAM 64	3
3	53700000	41	5120	QAM 64	4

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0

Network Log

Time Priority Description

24-11-2023 16:00:14	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 16:00:13	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:49:11	notice	REGISTRATION COMPLETE - Waiting for Operational status
24-11-2023 15:49:05	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:48:52	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:48:50	notice	Honoring MDD; IP provisioning mode = IPv4
24-11-2023 15:43:57	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:53	warning	ToD request sent - No Response received;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:33	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:33	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:13	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:13	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:54	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:15	warning	MDD message timeout;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:15	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:12	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:34	notice	REGISTRATION COMPLETE - Waiting for Operational status
24-11-2023 15:40:28	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:15	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:13	notice	Honoring MDD; IP provisioning mode = IPv4
24-11-2023 15:40:01	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:00	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:39:27	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:39:24	warning	ToD request sent - No Response received;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:33	warning	MDD message timeout;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:27	warning	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:27	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:22	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:21	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:18	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

legacy1
Alessandro Volta
2 years ago
No one said doing internet over Docsis would be perfect.
You got some bad jitter plus if the engineer did change your cables and such why does your BQM not show this?
Do you use HomePlug - Network Via Mains?
- Aedrothica
  On our wavelength
  2 years ago
  I used an old BQM I just realise. My mistake, that being said no Docsis internet won't always be perfect but since having everything tested and cables changed, why am I still experiencing the same issues I had before the engineer visit today? This should not be happing on a daily basis ALL day every few minutes... I'm not kidding, gaming for 12+ hours the past 2 days and I have issues EVERY couple minutes this is not normal and should not be happening, and did not happen previously.
  
  Nope, no homeplug, I am using ethernet directly into the hub.
  I have set up a new BQM so I shall post results tomorrow once it has updated, I'm certain it'll be all over the place.
  
  So any response from VM once that is done would be much appreciated, because I am honestly sick of it, there has to be a reason for these issues to still be happening.
  - jbrennand
    Very Insightful Person
    2 years ago
    Couple of things.. Switch the Hub off and unplug it from the mains supply for five minutes. Then switch the Hub back on and leave ~5 minutes When all done, check back in the settings and ensure that the RS error counts and any T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the PostRS and T3 ones) you have a problem.
    Secondly, what devices are plugged into the Hub on ethernet cables.? I ask because there have been several threads on here recently where similar BQM latency/packet loss problems were eventually pinned down to a dodgy piece of ethernet connected kit affecting the connection . Bad connectors on ethernet cables and faulty network switches being high on the list of culprits.
    What I advised was... if you run the BQM for 24h to get a picture of the issues (you have done this) - and then unplug all the ethernet cable connections from the Hub and just let it run - overnight is best - then in the morning look at the BQM and see if it has cleaned up. If it has - plug the devices back in one at a time for an hour or two until the problem reappears and that should indicate where to look for what is causing the issues
    
    Examples.
    See message 21 in the first thread, 13 in the second and 5 in the third
    https://community.virginmedia.com/t5/Networking-and-WiFi/Internet-connection-dropping/td-p/4781287/page/3
    https://community.virginmedia.com/t5/Networking-and-WiFi/Intermittent-Connection/td-p/5069984/page/2
    https://community.virginmedia.com/t5/Speed/Issues-in-GU22-area/m-p/5400109#M307543
legacy1
Alessandro Volta
2 years ago
Its not that hard to make anyone's BQM look bad with hubs and VM choose to not address it and yet they do other stuff like New Hub 5 Smart Security that we don't want!
Test hub in modem mode to a PC or console
- Aedrothica
  On our wavelength
  2 years ago
  I'm not sure why anyone would make their BQM look bad or make up issues though. I have a genuine problem I want to have fixed. Modem mode didn't seem to make a difference. I have now factory reset the hub.
  - Kath_P
    Forum Team
    2 years ago
    Hi Aedrothica,
    
    Thanks for taking the time to contact us via the Community. It's lovely having you on board with us in the Forums. ⭐
    
    We're sorry to hear you're having an issue with your broadband, despite having a recent engineer visit.
    
    Taking a look at things this end, it looks as though the hub is only connecting on 4 downstream channels. We will need to get another engineer out to double check things on the hub, at the cabinet and your external box too. As you've had a viit within the last few days, I'll book a senior engineer instead. I just need to confirm the address to ensure we are booking the visit on the correct account. I have sent you a direct message to allow us to do this with you in a private space. If you are using a PC/Laptop then you can just click on the little ✉ at the top right-hand side of the page to access your inbox. If you are on a mobile/tablet device then instead click on the little circle icon in the top right then select 'Messages'. 😊
    
    Thanks,
legacy1
Alessandro Volta
2 years ago
You don't have to know your doing it it can happened because of something you don't know of so if you tested in modem mode then that device might be whats causing it unless you know you was idle and doing a ping -t 194.168.4.100 that it spikes high then its VM thats the issue.

Forum Discussion

Network issues after engineer visit

Related Content

Account Issue

streaming to 2nd box buffering/network issues

Guest network

Virgin TV Go Home network issues

Engineer Missed Installation Date and Time