cancel
Showing results for 
Search instead for 
Did you mean: 

Constant Intermittent Dropouts, Status Shows Partial Service (US Only)

acha
On our wavelength

Hello, hoping someone can point me in the right direction before I try to get into contact with Virgin, I'd like to avoid a support chat if there is anything I can try myself 🙂

Recently (for the last few months) I have been getting consistent drop outs on my network connection. The dropouts last for 30-60 seconds and happen maybe once an hour, every hour.

So far I have tried a complete factory reset of the router (twice), which did not help the problem, and have confirmed the behaviour is exactly the same on WiFi or ethernet.

I had a look at the advanced router logs but there doesn't seem to be any clearly available guidance on acceptable ranges for Rx power, errors etc. (If anybody from Virgin ends up reading this, it would be useful to provide that information or at the very least have any out of range stuff checked on the automated network diagnostic).

Here is the info from my router:

Upstream bonded channels

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

14310002044.5512064 qam8
24960001944.8512064 qam7
32360004438.8512064 qam11
43010003441.8512064 qam10
53660002039.5512064 qam9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00400
2ATDMA00560
3ATDMA00670
4ATDMA00660
5ATDMA00560

Downstream bonded channels

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

12347500006.837256 qam13
22427500006.337256 qam14
32507500006.637256 qam15
4258750000737256 qam16
5266750000737256 qam17
6274750000737256 qam18
72827500007.437256 qam19
82907500007.137256 qam20
92987500006.137256 qam21
103067500005.537256 qam22
113147500006.937256 qam23
123227500007.337256 qam24
13330750000737256 qam25
143387500007.937256 qam26
153467500007.537256 qam27
163547500006.937256 qam28
17362750000737256 qam29
183707500007.437256 qam30
193787500006.637256 qam31
203867500005.537256 qam32
213947500005.936256 qam34
22402750000737256 qam35
23410750000737256 qam36
244187500006.537256 qam37



Downstream bonded channels

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

1Locked37.33287522549767
2Locked37.63062440224174
3Locked37.33051644511475
4Locked37.62857375749412
5Locked37.62553326726876
6Locked37.32222322707204
7Locked37.62153116687790
8Locked37.62157573662694
9Locked37.62258451643993
10Locked37.62644071640332
11Locked37.32351254609796
12Locked37.32319495564021
13Locked37.62004414498720
14Locked37.31782979444010
15Locked37.61661384416488
16Locked37.61792588406535
17Locked37.61932401395541
18Locked37.31782792372410
19Locked37.61981929372528
20Locked37.61882206348121
21Locked36.31827290293702
22Locked37.61464854235348
23Locked37.61418286199575
24Locked37.31335132170415

 

1 ACCEPTED SOLUTION

Accepted Solutions

Reece_MH
Forum Team (Retired)
Forum Team (Retired)

Hi acha 👋

I'm very sorry to hear that the issue is still ongoing. I've had a look at things on our end, and can see that the dropouts you are experiencing are direct to the Hub and can be caused by a cabling/incoming connection issue.

I'm going to send you a private message, so we can look into this further. Please look out for it in the top-right, white envelope.

Cheers,

Reece - Forum Team


New around here? To find out more about the Community check out our FAQ


See where this Helpful Answer was posted

25 REPLIES 25

acha
On our wavelength

And here is the router log:

Network Log

Time

Priority

Description

17/09/2023 17:51:23

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:59:36

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:59:36

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:57:5

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:57:5

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:44:9

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:44:9

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:44:7

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:44:3

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:48

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:40

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:39

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:36

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:36

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:32

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:32

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:31

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:31

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:29

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2023 15:43:29

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

jbrennand
Very Insightful Person
Very Insightful Person

Stats are awful - but can you start from a clean sheet and post again

_________________________

Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax and ethernet cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing. When its light, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. 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 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 (noise) that only a Tech visit will sort.
Also check the Upstream QAM’s are all at 64

 


--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

Tom_W1
Forum Team
Forum Team

Hi @acha thanks for your post here in the Community although we're sorry to hear of the concerns you've raised here.

We have ran some checks on your network and there aren't any issues on the line currently, so you shouldn't be facing any disruptions with your service.

How have things been since you posted, has there been any improvements?

Many thanks

Tom_W

acha
On our wavelength

Hi John,

Thank you for your detailed reply. Has been a very busy week at work! But will be trying this over the weekend and then I will post an update here.

 

acha
On our wavelength

Hi Tom,

Haven't had a chance to got through John's suggested steps yet. Will update once I have.

Just a note, I have two accounts, so the line you tested may be the wrong one, I have an address in Leeds (absolutely faultless) and one in London where the problems are.

Thanks for the update, let us know the outcome when you have had a chance to try the steps outlined. It also appears it was the correct connection checked by Tom also.

 

Rob

acha
On our wavelength

Hey all, so I followed the steps, internally reseated all connections including the coax cable on both ends, everything did indeed reset to 0. I couldn't see anything obvious with external cables.

Unfortunately after just 12 hours the stats are as follows:

Downstream bonded channels

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

12347500007.337256 qam13
21387500008.537256 qam1
31467500008.837256 qam2
41547500007.837256 qam3
5162750000837256 qam4
6170750000837256 qam5
71787500007.537256 qam6
81867500007.837256 qam7
91947500007.537256 qam8
102027500007.437256 qam9
112107500007.337256 qam10
12218750000737256 qam11
13226750000736256 qam12
142427500006.637256 qam14
15250750000737256 qam15
162587500007.137256 qam16
17266750000737256 qam17
182747500006.937256 qam18
192827500007.537256 qam19
202907500007.537256 qam20
212987500006.937256 qam21
223067500006.337256 qam22
233147500007.337256 qam23
243227500007.137256 qam24

Downstream bonded channels

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

1Locked37.3141454437095
2Locked37.669400543534
3Locked37.663850743035
4Locked37.376331343355
5Locked37.664620141756
6Locked37.668629844309
7Locked37.685026041868
8Locked37.393791942343
9Locked37.6107556939885
10Locked37.3133831440283
11Locked37.3140692841844
12Locked37.3145656339729
13Locked36.6163769538851
14Locked37.3147624138073
15Locked37.3126992539189
16Locked37.6115522036802
17Locked37.6105330135693
18Locked37.381041836557
19Locked37.671780636042
20Locked37.373408235700
21Locked37.381652233997
22Locked37.3103265034610
23Locked37.384402135629
24Locked37.3822601

34722

Upstream bonded channels

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

14310000039.3512064 qam8
24960000040512064 qam7
32360000037.8512064 qam11
43010000038.3512064 qam10
53660000038.5512064 qam9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00210
2ATDMA00170
3ATDMA00160
4ATDMA00110
5ATDMA0000

acha
On our wavelength

Also, not sure if this provides any insight but I checked the router status immediately during one of these problem points where the connection just hangs and it only showed one upstream channel:

Upstream bonded channels

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

13010000039512064 qam10

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00720

Hi acha, 

Thank you for reaching back out, I was able to locate you on our system and cannot see any issues, all specs are within spec, how have things been since  your last post on Saturday?

Regards

Paul.