Menu
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
789 Views
Message 1 of 12
Flag for a moderator

Bad connection back with a vengeance

I had problems before but the issue mysteriously resolved it self a month back, but yesterday and now especially today it has gone to hell, have a look:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0094c422c570b41182c167724f2c52adaf611681

 

0 Kudos
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
787 Views
Message 2 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

Downstream bonded channels

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

11387500005.537256 qam1
2146750000537256 qam2
31547500004.937256 qam3
41627500004.837256 qam4
51707500004.938256 qam5
61787500004.538256 qam6
71867500004.537256 qam7
81947500004.338256 qam8
92027500004.138256 qam9
102107500004.138256 qam10
112187500003.738256 qam11
122267500003.537256 qam12
132347500003.238256 qam13
14242750000338256 qam14
15250750000338256 qam15
16258750000338256 qam16
172667500002.738256 qam17
182747500002.738256 qam18
192827500002.938256 qam19
202907500002.938256 qam20
212987500002.737256 qam21
223067500002.738256 qam22
233147500002.738256 qam23
243227500002.538256 qam24
0 Kudos
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
786 Views
Message 3 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

Downstream bonded channels

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

1Locked37.6166781
2Locked38.6197670
3Locked38.61261033
4Locked38.6971049
5Locked38.6124978
6Locked38.61341047
7Locked37.61181053
8Locked38.6119987
9Locked38.6831052
10Locked38.668944
11Locked38.646984
12Locked38.6681039
13Locked38.642924
14Locked38.940877
15Locked38.651802
16Locked38.677897
17Locked38.676712
18Locked38.984690
19Locked38.964650
20Locked38.972596
21Locked38.6111660
22Locked38.6123610
23Locked38.9105549
24Locked38.6104500
0 Kudos
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
785 Views
Message 4 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

Network LogTime Priority Description
01/06/2021 11:10:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:10:19criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:10:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:10:7criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:07:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:07:33criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:04:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:04:56criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:03:44Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:03:44criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:03:40Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:03:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:58:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:58:33criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:57:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:57:16criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:56:43Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:56:43criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:51:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 10:51:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
784 Views
Message 5 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

I did a proper reset at about 9 am

0 Kudos
Reply
Adduxi
  • 5.62K
  • 461
  • 1.42K
Very Insightful Person
Very Insightful Person
779 Views
Message 6 of 12
Flag for a moderator

Re: Bad connection back with a vengeance


@LSky wrote:

I did a proper reset at about 9 am


DS power levels are okay, but you haven't posted US power levels.  Network logs are not so good. That's most likely noise on the circuit as shown by the PostRS errors.  All you can do is check all connections are "finger tight" from the Hub to outside omnibox.   Other that this, phone VM and get an engineer to investigate and fix.

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
LSky
  • 18
  • 0
  • 0
Tuning in
775 Views
Message 7 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

Upstream bonded channels

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

12580000048.3512016 qam11
23940000049.8512064 qam4
34620000050512064 qam3
43260000049512064 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Nah i am not calling them, that does not work.

0 Kudos
Reply
Adduxi
  • 5.62K
  • 461
  • 1.42K
Very Insightful Person
Very Insightful Person
741 Views
Message 8 of 12
Flag for a moderator

Re: Bad connection back with a vengeance


@LSky wrote:

Upstream bonded channels   <snip>

Nah i am not calling them, that does not work.


One of your US is nearly at max of 51 and needs adjusted.

If you are not going to ring, then just wait for a VM Mod to pick this thread up.  It can take several days however, as they are quite busy at present.

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

Zak_M
  • 6.12K
  • 315
  • 544
Forum Team (Retired)
Forum Team (Retired)
655 Views
Message 9 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

Good afternoon @LSky 

 

Welcome back to the forums and thank you for taking the time to post. 

 

I am sorry to hear that you are having some issues with your services. 

 

I have taken a look over the account and you are currently suffering with an area outage,  this is due to be resolved on the 04/06/21.

 

Kind regards,

Zak_M

 

 

0 Kudos
Reply
LSky
  • 18
  • 0
  • 0
Tuning in
553 Views
Message 10 of 12
Flag for a moderator

Re: Bad connection back with a vengeance

The connection is trash again, has been for few days, will this ever be resolved? I am having to use my phones connection to game with as my virgin media is so completely rubbish.

0 Kudos
Reply