cancel
Showing results for 
Search instead for 
Did you mean: 

Frequently failing internet connection

simonjb
Tuning in

Hello.

Since the end of last weekend my internet connection has been failing at least once a day.  Sometimes it's "just" a temporary (one minute or so) loss of connectivity (enough to kick me off a video call) but at other times the Superhub reboots itself.  Sometimes it doesn't recover again and I need to power cycle it.

The Superhub is running in modem mode, connected to a Netgear Orbi mesh system (which is working absolutely fine, as far as I can tell - I still have connectivity to local servers etc. in the house).

Reading other threads on this forum and looking at what's in the logs it appears that there might be "noise" on the coax line.  I've reported the problem to VM over the phone this morning (c.11.30); they said they have increased the power on the line but I'm not convinced that's the issue, and it certainly hasn't fixed the problem.

Superhub logs / config and BQM to follow.

This sounds like a physical cabling issue to me.  Does this need an engineer out to take a look?  Thanks in advance for any help.

32 REPLIES 32

Hi,

I already have a BQM running.  Here's today's graph (the outage around 8am is when I did the factory reset of the hub, as requested yesterday):

https://www.thinkbroadband.com/broadband/monitoring/quality/share/645e550b9803d6e6c75aa6e02b59c9637cf9e7d2-24-06-2021

 

...and here's yesterday's:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/a89fa73eb923cd85d1a21ba5f63291c6a040c1c9-23-06-2021

The internet connection has just failed again.  It really is very unstable.  Same messages as usual - I will post below for completeness.

Network Log

Time Priority Description

24/06/2021 14:31:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:37criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:35criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:31:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:30:18Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:30:18criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2021 14:27:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream and upstream data from the hub (NB the modem was power-cycled and factory reset at 8am this morning, so these error counts are after less than 8 hours):

Downstream bonded channels

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

1370750000-1.730256 qam26
2202750000131256 qam9
32107500000.931256 qam10
42187500000.731256 qam11
52267500000.531256 qam12
62347500000.731256 qam13
72427500000.530256 qam14
82507500000.230256 qam15
92587500000.230256 qam16
10266750000030256 qam17
11274750000-0.430256 qam18
12282750000-0.530256 qam19
13290750000-0.530256 qam20
14298750000-0.530256 qam21
15306750000-0.730256 qam22
16314750000-0.730256 qam23
17322750000-0.930256 qam24
18330750000-0.930256 qam25
19378750000-2.530256 qam27
20386750000-2.730256 qam28
21394750000-2.530256 qam29
22402750000-2.430256 qam30
23410750000-2.530256 qam31
24418750000-2.430256 qam32



Downstream bonded channels

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

1Locked33.48384390016
2Locked34.417181788277
3Locked34.31457409485
4Locked34.419452078028
5Locked34.42157411449
6Locked33.941063068132
7Locked33.861162477668
8Locked33.5596586680
9Locked33.578533047330
10Locked33.47146283043
11Locked33.48739342096
12Locked33.3124071047354
13Locked32.9172613021355
14Locked331468628612
15Locked3313162110744
16Locked33125904400
17Locked3311530335128
18Locked33.39015302868
19Locked33.37903246260
20Locked33.46121334971
21Locked33.481721556376
22Locked33.47634461304
23Locked33.391571205714
24Locked33.38168354569

 

Upstream bonded channels

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

13940000042.3512064 qam6
22580000040.8512064 qam8
33260000042512064 qam7
44620000044512064 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0010
3ATDMA0000
4ATDMA0000

 

From what I understand, the SNR on the downstream is too low - should be >34.  This seems odd as the engineer tested the line and couldn't find any problem last Saturday.  But looking back over the stats I've taken from the hub over the last couple of weeks, the SNR (in fact, all the figures) seem to vary a fair bit.  Is it possible that something is intermittently producing noise on the line? 

Thanks for coming back to us @simonjb,

 

I've requested that an engineer comes to revisit the property to take another look at the connection for you

 

Pleas log into your self-care account to view the time and date of the visit and you will be free to rearrange this if required

 

Kindest regards,

 

David_Bn

Thank you David.

Just an update after the engineer visit....

The engineer came a week ago and renewed all the cables and connectors, including removing a _very_ old CATV/FM radio splitter (I think the cable was installed to the house 30 years ago and hasn't been changed since).

Since the engineer visit the connection has been stable.  I can see very few errors in the log and the SNR is now 38 dB across all downstream channels.

I'm hopeful that this has fixed the problem, but will continue to monitor, especially if the weather gets hot again (there did seem to be some correlation between the worst problems and very hot weather).  Thanks everyone for your help.

Simon.

No problem!

Keep us posted! - The problems in hot weather can be caused by the expansion of the cable leading to a change in power levels - normally if you are firmly within the spec all is fine and you notice nothing - However if you are close to tolerance - a small change in power can tip over the edge and cause issues!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

Travis_M
Forum Team (Retired)
Forum Team (Retired)

Be sure to keep us updated on this @simonjb 🙂

 

Glad to hear you've seen an improvement

 

Regards

Travis_M
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs