New Virgin Media SuperHub 3 ... issues

After a few issues with my old router (2ac) Virgin swapped me onto a new hub 3 ... and since then I have been getting T3 ranging issues, random router restarts and general internet disconnections. In an effort to build up some evidence to club Virgin with (after 2 engineer visits saying everything was in spec and working) I started using the BQM.

I can clearly see the times the internet drops out completely (red bits) but I'm not sure about the rest of the monitor results. Can anyone tell me if this is "normal" for a Superhub 3 because so far I am completely underwhelmed and wish they had left me on the 2ac.

Standard specification compliant : DOCSIS 3.0
Hardware version : 10
Software version : 9.1.116V

My BQM

Suggestion from me is that your Superhub 3 has not had the Intel Puma 3 chip bug patches yet, i.e. based on the yellow jitter.

I don't recall the version numbers that have the Puma fix in them.

In terms of moaning at Virgin, is the BQM showing the same as what you get if you do some many pinging of locations. Need to do this as support will usually just blame our BQM tool, when the tool is working perfectly - one problem can be that the LINX routing out of Virgin Media is congested on their side of things but as your issue is 24.7 its not that

My Broadband Ping

My Broadband Ping

My Broadband Ping

Monday, Tuesday, Wednesday this week.

Trying to do a bit of video chat tonight to see if it's better, but it's been unsable for voip or video, gaming, streaming (up or down), and it's been a nightmare to play videos.

Research I have done suggests the Superhub 3.0 is unfit for purpose as previous post suggests, around unfixable problems on the Puma chipset that the patch can only slightly alleviate.

Was on the phone to virgin, was told 'no such patch exists', then 'even if a patch did exist...' only to have the virgin media twitter confirm it was being rolled out the following day.

They lie and use every trick in the book to make it seem like you're the one being unreasonable. I believe it is referred to as gaslighting. They have known about this for years. I tried to leave in October, but they wouldn't let me. Now I have BQM.

Current firmware version (the one with the problems) v9.1.166

Being rolled out (that ameliorates but can't fix) v9.1.166.608 (or .603, it's unclear)

Edited by edplaysjazz (Wed 20-Jun-18 21:42:22)

using the router in modem mode or getting the SU2 or business hub seems to be the only way to fix it

it not fix the packet loss thought as that's typically network issues norm the COXAL side (cable issues power to high or too low), what are your power levels like on your suerhub, if your seeing packet loss in BQM VoIP and streaming will become problematic

https://www.thinkbroadband.com/broadband/monitoring/...

after your router is in modem mode (plug your own router in) it should look like the above (before 3am SU3 in router mode and after in modem mode with a RT-AC66U_B1 used) Note IP address will change so you need to update the IP address your monitoring unless your using DDNS pointer

Hello,

Is anyone having problems with BQM on the Virgin Superhub v3.0? I had BQM monitoring going for weeks without any issues but recently, last few days, BQM is interrupted and I just get a solid red block until I edit the monitor and it starts again.

Bob

Well, now editing the monitor doesn't work either. Have Virgin done something overnight to block BQM monitoring?

Anyone else have this issue?

Mine and my friends are doing the same. They might have introduced some sort of automatic blocking for multiple pings as though it is being attacked.

Have had the same issues as above. Seems to go to 100% packet loss and then if you edit the BQM it will start pinging again.

I believe I have received the latest SuperHub 3 firmware in the last week. Have attached a snapshot of the last 24 hours and then one from a week ago. Hub is showing firmware version 9.1.116.608

My Broadband Ping Last 24 hours.

My Broadband Ping Last Sunday.

Yes, that looks just like mine.

and I'm on the same firmware version too ... pity ... not sure if there's anyway round it, maybe delete and start afresh?