Packet Loss

[cor3ys]

I have been on the 1 gig service since October 2021 and have never had an issue at all.

On the 12th August i received a Text that work was being carried out in my area and on the 15th august i received another text to say work was completed. since the 15th August i have suffered from packet loss which i have never done before on this service...

BQM from the 15th August 

I left it a couple of weeks to see if it settled down BQM for 2nd September

and now todays, one month on i am still getting packet loss which keeps dropping my internet out

I have never suffered packet loss until you carried out some works on the 15th August...

3.0 Downstream channels

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

26	339000000	0.200001	40.946209	QAM256	26
1	139000000	0.200001	40.366287	QAM256	1
2	147000000	-0.099998	40.366287	QAM256	2
3	155000000	0.000000	40.946209	QAM256	3
4	163000000	-0.299999	40.946209	QAM256	4
5	171000000	-0.599998	40.946209	QAM256	5
6	179000000	-0.799999	40.366287	QAM256	6
7	187000000	-1.099998	40.366287	QAM256	7
8	195000000	-1.299999	40.366287	QAM256	8
9	203000000	-1.000000	40.946209	QAM256	9
10	211000000	-0.900002	40.366287	QAM256	10
11	219000000	-0.900002	40.946209	QAM256	11
12	227000000	-0.799999	40.946209	QAM256	12
13	235000000	-0.900002	40.946209	QAM256	13
14	243000000	-0.700001	40.366287	QAM256	14
15	251000000	-0.299999	40.946209	QAM256	15
16	259000000	0.400002	40.946209	QAM256	16
17	267000000	0.599998	40.946209	QAM256	17
18	275000000	0.900002	40.366287	QAM256	18
19	283000000	0.500000	40.366287	QAM256	19
20	291000000	0.200001	40.946209	QAM256	20
21	299000000	0.200001	40.366287	QAM256	21
22	307000000	0.500000	40.946209	QAM256	22
23	315000000	0.500000	40.946209	QAM256	23
24	323000000	0.400002	40.946209	QAM256	24
25	331000000	0.099998	40.946209	QAM256	25
27	347000000	0.299999	40.946209	QAM256	27
28	355000000	0.200001	40.366287	QAM256	28
29	363000000	0.200001	40.946209	QAM256	29
30	371000000	0.299999	40.946209	QAM256	30
31	379000000	0.299999	40.366287	QAM256	31

3.0 Downstream channels

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

26	Locked	40.946209	0	0
1	Locked	40.366287	0	0
2	Locked	40.366287	0	0
3	Locked	40.946209	0	0
4	Locked	40.946209	0	0
5	Locked	40.946209	0	0
6	Locked	40.366287	0	0
7	Locked	40.366287	0	0
8	Locked	40.366287	0	0
9	Locked	40.946209	0	0
10	Locked	40.366287	0	0
11	Locked	40.946209	0	0
12	Locked	40.946209	0	0
13	Locked	40.946209	0	0
14	Locked	40.366287	0	0
15	Locked	40.946209	0	0
16	Locked	40.946209	0	0
17	Locked	40.946209	0	0
18	Locked	40.366287	0	0
19	Locked	40.366287	0	0
20	Locked	40.946209	0	0
21	Locked	40.366287	0	0
22	Locked	40.946209	0	0
23	Locked	40.946209	0	0
24	Locked	40.946209	0	0
25	Locked	40.946209	0	0
27	Locked	40.946209	0	0
28	Locked	40.366287	0	0
29	Locked	40.946209	0	0
30	Locked	40.946209	0	0
31	Locked	40.366287	0	0

[cor3ys]

All my upstream's have now gone to QAM32 instead of QAM64 and had another 18 T3 timeouts today...

Upstream bonded channels

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

0	49600000	48.8	5120	QAM 32	9
1	43100000	46.8	5120	QAM 32	10
2	36600000	48.5	5120	QAM 32	11
3	30100000	48.8	5120	QAM 32	12
4	23600000	48.3	5120	QAM 32	13

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	18	0
1	ATDMA	0	0	18	0
2	ATDMA	0	0	18	0
3	ATDMA	0	0	18	0
4	ATDMA	0	0	18	0

Network Log

Time Priority Description

08-01-2023 11:45:09	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:45:09	warning	Dynamic Range Window violation
08-01-2023 11:45:09	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:45:09	warning	Dynamic Range Window violation
08-01-2023 11:45:09	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:45:09	warning	Dynamic Range Window violation
08-01-2023 11:43:36	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;
08-01-2023 11:43:36	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:54	critical	16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:42	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:41	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:41	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:18	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:03	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-01-2023 11:08:03	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;

[cor3ys]

Another week pass and still i am getting daily packet loss and huge latency spikes for no reason. with no feedback on how this is going to be fixed after 4 tech visits now...

Network Log

Time Priority Description

19-01-2023 10:23:30	notice	CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 527971; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:24	warning	Unicast DSID PSN startup error
19-01-2023 10:23:20	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;
19-01-2023 10:23:20	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:17	notice	REGISTRATION COMPLETE - Waiting for Operational status
19-01-2023 10:23:11	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:11	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;
19-01-2023 10:23:11	warning	Dynamic Range Window violation
19-01-2023 10:23:11	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:11	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:11	warning	Dynamic Range Window violation
19-01-2023 10:23:11	warning	Dynamic Range Window violation
19-01-2023 10:23:11	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:11	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:11	warning	Dynamic Range Window violation
19-01-2023 10:23:11	warning	Dynamic Range Window violation
19-01-2023 10:23:06	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:23:05	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:58	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:56	notice	Honoring MDD; IP provisioning mode = IPv4
19-01-2023 10:22:45	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:40	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;
19-01-2023 10:22:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:20	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;
19-01-2023 10:22:02	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:01	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;
19-01-2023 10:21:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:21:40	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;
19-01-2023 10:20: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;
19-01-2023 10:20:26	warning	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:20:23	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Downstream bonded channels

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

1	Locked	42	9446	1773
2	Locked	42	14552	2198
3	Locked	42	15278	2010
4	Locked	42	10121	1965
5	Locked	42	10950	1186
6	Locked	42	15400	1959
7	Locked	42	17089	1651
8	Locked	42	18916	2090
9	Locked	42	12834	1913
10	Locked	42	8990	1664
11	Locked	42	5871	1428
12	Locked	42	5330	1702
13	Locked	42	9236	1049
14	Locked	42	20789	1766
15	Locked	42	15728	2037
16	Locked	42	9540	2094
17	Locked	42	7274	2026
18	Locked	43	3786	1866
19	Locked	42	2718	1794
20	Locked	42	2309	1759
21	Locked	42	2709	1868
22	Locked	42	3156	2011
23	Locked	42	3433	2250
24	Locked	42	3196	2178
25	Locked	42	2810	2144
26	Locked	41	2452	1801
27	Locked	43	2127	1685
28	Locked	42	2090	1394
29	Locked	42	2218	1748
30	Locked	42	2330	1945
31	Locked	42	2404	1876

[legacy1]

BQM for today shows mostly fine did you reboot the hub 10:20am?

How is the connection in modem mode?

could be a faulty amp 

[cor3ys]

Statement from Virgin Media..

Okay so I have heard back from the network team and they have advised me we have done all we can for you unfortunately.

They have looked into everything even other customers on your street.

They have advised what you are seeing would be very little impact to your services. 

 All residential services will be sharing the network so there are instances where we can see very short packet loss events caused by other factors outside our control.

There will be very few homes that will never have any packet loss. 

Now the only way you are going to have a perfect line is by having your own line and right now this offered to our business customers, so it could be worth having a chat with the business line.

They have ensured and promised me they've done everything they can do and no matter what provider you will be you will get the same issue from time to time. 

These are some of the factors which could impact the packet loss 

1. The spike could be generated by a poor performing Thinkbroadband testing server.
2. The routing of the testing pings from our network to the Thinkbroadband site could be congested (this would sit outside our network).
3. The service could be affected by environmental electrical issues such as a thermostat arching as it switches on and off.

When they tested the connection using the OFCOM Testing methodology they saw very little signs of a packet loss issue and the rates we are seeing are not customer impacting. 

So I am sorry this is the news you didn't want but we will not be able to do anything else on this matter.

The only thing you could do swap your account to the business line.

I am sorry again but at least we give this a very good go and trying to get it fixed. Thanks 

Network logs from the hub clearly rule out items 1 & 2

19-01-2023 10:22:56	notice	Honoring MDD; IP provisioning mode = IPv4
19-01-2023 10:22:45	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:40	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;
19-01-2023 10:22:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:20	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;
19-01-2023 10:22:02	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:22:01	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;
19-01-2023 10:21:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:21:40	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;
19-01-2023 10:20: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;
19-01-2023 10:20:26	warning	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 10:20:23	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[cor3ys]

no, no hub reboot, and yes in modem mode..

daily packet loss...

Sunday

Monday

[legacy1]

Trouble with tech is anything can be problem and the more you add the more possible problems can happen.

So to limit what could be the cause you need modem mode with a connected PC (no router) and allow BQM on the firewall.

Problem is likely a intermittent fault with Docsis that may be hard to pin down    

Could also be a the hub docsis handling over 24Hr or CMTS handling over 24Hr 

[thinksingle]

At least you have had networks investigate your issue and on the brighter side at least your connection doesn't look as bad as mine. I frequently have no connection after 12-1AM too. Not to mention the packet loss and jitter almost 24/7.

For almost 4 months...

[cor3ys]

---

@legacy1 wrote:

Trouble with tech is anything can be problem and the more you add the more possible problems can happen.

So to limit what could be the cause you need modem mode with a connected PC (no router) and allow BQM on the firewall.

Problem is likely a intermittent fault with Docsis that may be hard to pin down    

Could also be a the hub docsis handling over 24Hr or CMTS handling over 24Hr 

---

Virgin media have made it clear, if i want a good line then i need to purchase a business line, they have no further interest.....

[cor3ys]

---

@thinksingle wrote:

At least you have had networks investigate your issue and on the brighter side at least your connection doesn't look as bad as mine. I frequently have no connection after 12-1AM too. Not to mention the packet loss and jitter almost 24/7.

For almost 4 months...

---

Yeh mine started from a network upgrade 4 months ago, this is what they left me with. up until then i had perfect connection there is only 6 people in the cabinet including me and everything is brand new as it was a new street install... now i know why there is only 6 of us in the cabinet word has got round and no one wants Virgin media... 

[Adduxi]

---

@cor3ys Virgin media have made it clear, if i want a good line then i need to purchase a business line, they have no further interest.....

---

The “business line” is exactly the same cables as your Residential line, except you get a different Hub and an SLA.