I know some people have had issues with the Hub 4 as well, but I have not long moved from a Hub 4 to a Hub 5, because I wanted the 2.5G port to benefit certain devices and max out the connection. I never experienced an issue with the Hub 4 and I had very consistent ping times of 6/7ms and latency on both download and upload <18ms at all times. However, since getting the Hub 5, I have have worse latency and awful latency spikes. Speed is on point, but latency sucks. Sites that measure buffer bloat have downgraded me from an A to B rating and low latency gaming is suffering.
My kit: Hub 5 in modem mode > 2.5G eth port > OPNsense box with ample capacity. I use Unifi access points (all testing done via cable anyway). Even if my kit were the issue, which it is not, I would have had the same issues with the Hub 4.
So much for Virgin's latest DOCSIS hub. If I had known it was going to be this bad, I wouldn't have bothered getting it.
Before anyone asks - nothing else on my network has changed, I literally swapped it out with the Hub 4 and now I have this.
Any ideas? Can I get a new hub to see if that does it?
Btw, I tried posting images of the testing in the post above and I kept getting errors. As soon as I remove them, it works... your forum is even borked.
I'll try again in this post on a 3rd party site:
Please ignore dropped packet areas, this is not a problem I have (thankfully) they are either rebooting the Hub to troubleshoot or scheduled downtime.
Check the Upstream / Downstream status tabs for signal level issues / errors.
See if the same issue persist via a Hub 5 1Gb/s port.
The Hub 5's 2.5GB/s port expects the connected device to have EEE Disabled, set the WAN port of the OPNsense box to have "Energy Efficient Ethernet" Disabled.
I'm a LAN guy so I'll have to let someone else interpret DOCSIS. Although it looks like no uncorrectable errors on the down, and a lot of corrected ones.
Your going to hit some latency with download or uploading due to no BWM plus your high speed means when you do download or upload and the bandwidth shared in the area is at high load that you can't hit your speed will mean VM deal with what bandwidth you can have and any latency impacts.
I'm looking at the stats and apart from one US channel with T3 errors, the rest are fine. The DS 3.1 correctable count is always high on the Hub 5 for some reason, mine is 332275527 at the moment.
As for the BQM's they are looking not bad, considering some of the other BQM's that are posted here.
Not sure what you will be able to get done really going on this evidence?