cancel
Showing results for 
Search instead for 
Did you mean: 

Constant dropping of Internet/wifi in first week of service

JonReese
On our wavelength

Hi all,

I had my Virgin Media broadband activated just under a week ago (the previous owner had already had it installed, so it was just a case of setting my new router up). However we have been seeing constant issues with either the connection to the router itself dropping (i.e. the wifi) or the Internet connection to the router completely dropping too. I thought for the first couple of days it might be the engineers testing the line but as it has been 6 days now, I'm guessing there are other issues. I've checked online to see if there are any issues in my local area, and all seems well. I've even changed the network name and all the settings (upgraded the security to WPA2, etc), and have done a reset via the pin button on the back of the router a couple of times.

I will eventually buy and set up a mesh network to improve the overall signal and performance of the connection, but I'd like to ensure the connection is stable prior to doing that! It isn't an issue with signal as I have had connection problems in the same room as the router. I've noticed a lot of downstream errors in the network status section of the router page. I'll add all the stats now just in case anyone has an idea what the problem might be. Please note I reset the Hub 3.0 about 30 minutes ago, so I assume all the error stats were reset prior to that.

Cable Modem StatusItemStatusCommentsAcquired Downstream Channel (Hz)

330750000
Locked

Ranged Upstream Channel (Hz)

60300180
Locked

Provisioning State

Online

 

Downstream bonded channels

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

13307500001.238256 qam25
2202750000-138256 qam9
3210750000-2.738256 qam10
4218750000-3.738256 qam11
5226750000-3.738256 qam12
6234750000-3.538256 qam13
7242750000-2.238256 qam14
8250750000-0.538256 qam15
9258750000038256 qam16
10266750000038256 qam17
11274750000-1.438256 qam18
12282750000-2.538256 qam19
13290750000-2.438256 qam20
14298750000-238256 qam21
15306750000-138256 qam22
163147500000.538256 qam23
173227500001.238256 qam24
183387500000.438256 qam26
19346750000-0.738256 qam27
20354750000-138256 qam28
21362750000-0.738256 qam29
22370750000038256 qam30
233787500001.440256 qam31
243867500001.938256 qam32



Downstream bonded channels

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

1Locked38.617023021
2Locked38.919514229
3Locked38.922314037
4Locked38.624893398
5Locked38.625803427
6Locked38.630634064
7Locked38.958872833
8Locked38.925984001
9Locked38.923774485
10Locked38.926452577
11Locked38.923953658
12Locked38.622872079
13Locked38.625193021
14Locked38.628762061
15Locked38.626232287
16Locked38.922892733
17Locked38.618781281
18Locked38.916811136
19Locked38.918322328
20Locked38.919901440
21Locked38.621081565
22Locked38.921351667
23Locked40.320501557
24Locked38.916312320

 

Upstream bonded channels

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

16030018044.3512064 qam1
25370042554512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0030
2ATDMA0000

 

I thought I'd come here prior to phoning customer service and potentially having an engineer booked if it is an issue that could be sorted without that!

Thank you in advance!

14 REPLIES 14

JonReese
On our wavelength

Thanks so much Andrew for your informative reply. Since I did a pinhole reset on Monday, I had 4 upstream channels until last night - now I have 3! And the post-RS errors on the downstream are still rising high. All coax (and other) connections have been adjusted and are completely fine.

Good point about the cooling off period. Can someone from VM please look into this ASAP or I won't really have much option but to look to another provider.

Thank you.

When a hub gets rebooted, it renegotiates all channels from scratch, and that's a good way of fixing a connection that'd drifted off a bit.  That's why things usually look improved after a reboot.  The protocols the hub uses are supposed to keep everything ticking over nicely as it runs, generally they work well but sometimes needs that extra "kick", and they can't improve a fault that (like most faults) has a physical cause, like a damaged joint, a crimped or abraded coax cable, a fault line amplifier or the like.

If the underlying problem of a noise fault isn't found and fixed, then the problem recurs, as you might expect.  A further reboot might temporarily help if the problem crops up again, but that's not a viable solution for a poor quality connection - it needs to work as advertised.  You can try calling this in by phone as a reliability problem, and see how you rate VM's telephone support, factor that into your view of how to proceed.  Any tech support agent who says it is anything to do with your wifi, or "we'll send a special signal to your hub", or "it'll settle down over the next few days" would be deliberate fobbing off.  This needs a technician visit, and with an intermittent fault there's a possibility that you won't see a first time fix, you'd then be outside the cooling off period.

I'm not encouraging you to cancel: When it works reliably and as advertised, then VM is a good service and even at non-discounted prices the phone and internet packages are good value.  I've been with VM for 25 years, that may tell you something.  However, when things go wrong, you might reasonably conclude that VM's telephone support is outsourced to the same company that operates the Iranian Revolutionary Guards customer care line, and that every Virgin Media process, every tool, every contact channel, they all take design inspiration from Franz Kafka, and staff leadership from Mr Bean.  If you really need the speed and can't get anything acceptable as an alternative, then stick with it, and VM will eventually get this fixed, although in some cases customers need to be very persistent.  Getting complex or intermittent faults solved very occasionally takes months.

JonReese
On our wavelength

Yeah restarting the router was a kind of last resort to see if it was an issue with it negotiating a connection or something (clearly I'm no network engineer!).

Had massive issues last night and this morning as well, so there's definitely an underlying problem, and I think I've given it long enough to show as evidence that it needs an engineer to fix it. Customer services on Twitter are much faster at responding, so I asked them yesterday to get someone to look at this page, but it seems that hasn't happened yet. Guess I'll have to use their dreaded phone service later on today if I get no response this morning.

Thanks again for the help @Andrew-G.

JonReese
On our wavelength

Why do they always think they can fob you off and pretend that an issue is being looked into, when we all know it isn't?!

Screenshot 2022-03-24 at 09.34.13.png

Had the same message on Sunday 😂

Hi JonReese,

Thanks for posting on our community forums. Sorry to her that you're still experiencing issues with your connection and down stream power level issues. 

Remotely checking they systems from our end, we can see that you have had an engineer attend recently. 

How have things been since the visit? Has anything improved?

Kind regards Jodi.