Menu
Reply
  • 632
  • 18
  • 76
Fibre optic
280 Views
Message 1 of 8
Flag for a moderator

Broadband back to being rubbish in the early/late evenings

BQM-19102020.JPGSince about March my BB is back to the ways of old, I've been through 2 bouts of contention/over subscribed and it looks like the problem may now be back.

I've contacted CS via phone and used the online service check and they claim everything is fine but I get slow downs in the early to late evenings. With COVID it's almost impossible to speak to somebody about this with most calls being automated which then basically seem to hang up.

Could/would a kind mod here please check for me if there is an a current over utilised fault in my area, when the fault was lodged and when is the next review date please?

If there is no existing fault and clearly there is an issue in the evening, I've spoken to my neighbours and they experience the same then can somebody please investigate.

I've attached a BQM graph from yesterday/today. 

________________________________________________________________

In HA7. Billing Area 21.
Utilisation Fault
F003502423: Review Dates -> 07/10/2015 -> 02/12/2015 -> 20/01/2016 😞 -> Closed 🙂
Utilisation Fault F004873444: Review Dates -> 29/03/2017 😞 -> Closed 🙂
Utilisation Fault F005506920: Review Dates -> 09/08/2017 -> 08/06/2018 -> 13/06/2018 -> 11/07/2018 -> 12/09/2018 -> 29/05/2019 😞 -> Open 😞


0 Kudos
Reply
  • 12.28K
  • 950
  • 1.58K
Alessandro Volta
267 Views
Message 2 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

Can you post a 'Live Link' to your BQM please ...

Instructions for posting BQM Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

In the URL box paste the link you copied and in the ‘text to display’ box write My BQM then click OK - you can post the link straight away.

Then

 

Can you please

Type 192.168.0.1 (192.168.100.1 in Modem mode) into your browser URL bar and press enter. 

Hub 2 & 3 When the page appears DO NOT LOG IN but click ‘Check Router Status’.

Hub 4 When the page appears LOG IN then click ‘Check Router Status’.

Copy and paste the contents of the Downstream, Upstream and Network Log tabs onto here, if you get a yellow warning click the Post button again. Use one post for each tab if you wish. Please do not use screen grabs.

A Guru will be along soon to decipher the info.

***********************************************************************************************************************************

Mike Robinson
Semi-Retired Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.

My Broadband Ping - Mike Robbo
  • 632
  • 18
  • 76
Fibre optic
249 Views
Message 3 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

My BQM 

Had to create seperate posts as I think altogether it exceeds the max characters allowed.

________________________________________________________________

In HA7. Billing Area 21.
Utilisation Fault
F003502423: Review Dates -> 07/10/2015 -> 02/12/2015 -> 20/01/2016 😞 -> Closed 🙂
Utilisation Fault F004873444: Review Dates -> 29/03/2017 😞 -> Closed 🙂
Utilisation Fault F005506920: Review Dates -> 09/08/2017 -> 08/06/2018 -> 13/06/2018 -> 11/07/2018 -> 12/09/2018 -> 29/05/2019 😞 -> Open 😞


0 Kudos
Reply
  • 632
  • 18
  • 76
Fibre optic
248 Views
Message 4 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

Downstream bonded channels

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

13227500004.538256 qam24
22027500003.940256 qam9
32107500003.938256 qam10
42187500003.740256 qam11
52267500003.538256 qam12
62347500003.438256 qam13
72427500003.738256 qam14
8250750000440256 qam15
9258750000440256 qam16
10266750000438256 qam17
11274750000438256 qam18
122827500004.340256 qam19
132907500004.340256 qam20
142987500004.838256 qam21
153067500004.538256 qam22
163147500004.538256 qam23
173307500004.640256 qam25
183707500003.738256 qam26
19378750000438256 qam27
203867500004.538256 qam28
213947500004.538256 qam29
22402750000438256 qam30
234107500004.338256 qam31
244187500004.338256 qam32


Downstream bonded channels

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

1Locked38.621035235
2Locked40.3407812367
3Locked38.9159322815
4Locked40.348216182
5Locked38.942317458
6Locked38.9417914424
7Locked38.9292012308
8Locked40.3257410996
9Locked40.3221811046
10Locked38.9217511756
11Locked38.9222312191
12Locked40.3256911898
13Locked40.3278010572
14Locked38.9507911988
15Locked38.926579701
16Locked38.9216311336
17Locked40.3205411227
18Locked38.6427210761
19Locked38.9212310645
20Locked38.9199410973
21Locked38.9226710122
22Locked38.920228743
23Locked38.622228113
24Locked38.921808818

 

Upstream bonded channels

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

16030041244.3512064 qam1
23940009043.8512064 qam4
34620007843.8512064 qam3
45370014144512064 qam2


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0020
2ATDMA0030
3ATDMA0000
4ATDMA0010

 

________________________________________________________________

In HA7. Billing Area 21.
Utilisation Fault
F003502423: Review Dates -> 07/10/2015 -> 02/12/2015 -> 20/01/2016 😞 -> Closed 🙂
Utilisation Fault F004873444: Review Dates -> 29/03/2017 😞 -> Closed 🙂
Utilisation Fault F005506920: Review Dates -> 09/08/2017 -> 08/06/2018 -> 13/06/2018 -> 11/07/2018 -> 12/09/2018 -> 29/05/2019 😞 -> Open 😞


0 Kudos
Reply
  • 632
  • 18
  • 76
Fibre optic
247 Views
Message 5 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

Network Log

Time Priority Description

19/10/2020 11:46:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/10/2020 09:30:27ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 21:19:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 13:00:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 13:00:8criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 13:00:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:56Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:51criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:51Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:51criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:47Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:47criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:47Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:47Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:42criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:59:41Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:58:55Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:58:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/10/2020 12:58:50criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
________________________________________________________________

In HA7. Billing Area 21.
Utilisation Fault
F003502423: Review Dates -> 07/10/2015 -> 02/12/2015 -> 20/01/2016 😞 -> Closed 🙂
Utilisation Fault F004873444: Review Dates -> 29/03/2017 😞 -> Closed 🙂
Utilisation Fault F005506920: Review Dates -> 09/08/2017 -> 08/06/2018 -> 13/06/2018 -> 11/07/2018 -> 12/09/2018 -> 29/05/2019 😞 -> Open 😞


0 Kudos
Reply
  • 2.23K
  • 144
  • 433
Problem sorter
235 Views
Message 6 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

Poor logs and high PostRS errors, would point to noise in the circuit, hence the loss of sync.  As I'm sure you are aware, an engineer will need to diagnose.

Good luck !

0 Kudos
Reply
  • 4.48K
  • 758
  • 1.82K
Very Insightful Person
Very Insightful Person
227 Views
Message 7 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings

...or they might point to the open over-utilisation fault that is apparently noted in the OP's signature block?

And looking at the disgraceful history recorded in the closed faults, I can't understand why the OP continues to give their business to VM.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
  • 2.23K
  • 144
  • 433
Problem sorter
180 Views
Message 8 of 8
Flag for a moderator

Re: Broadband back to being rubbish in the early/late evenings


@Andruser wrote:

...or they might point to the open over-utilisation fault that is apparently noted in the OP's signature block?

And looking at the disgraceful history recorded in the closed faults, I can't understand why the OP continues to give their business to VM.


There are several users on this Forum and on CableForum who stay with VM despite faults.  It may be they have no other choice.  However with the approach of 5G and good Wifi routers, that could change.?

0 Kudos
Reply