Just seen this on the register website, a firmware update is due it says
Due when though, that's the question haha. We haven't even had the last firmware update yet (the one that was being rolled out 'in November'). We also see this laggy ping issue on the SH3. Our TBM graphs look just like those above, but we get extra packet loss for the lulz. I'll look forward to patched firmware - complete with new bugs features - some time in late 2017.
Thanks @datalink, this ties in quite nicely with my experience as well... combined with a high local density and a segmentation project that keeps being delayed, it all pushed me to get a VDSL connection which I now use as my primary, and I've left the HFC connection for downloads only.
Output below is from the same source outbound over two separate virgin media links.
The source is local to the first site and over a private link to the second (latency introduced by the link is approximately 4ms).
1.) Virgin Media Superhub3 200Mbps
2.) Virgin Media Superhub 2 - 150Mbps
This is a plot of 5 pings sent every minute to the locale google cache server, this is real world oputput not testing. As you can see there is some delay introduced by the server but this is mirrored in both graphs.
The Superhub 3 has a similar latency despite being 4ms closer to the server and a much higher jitter.
I've asked VM if they would consider lifting the swap-embargo on Superhub 2 ACs, so that people who find the hub 3.0 too troublesome would be able to call in and get a swap to a 2AC. Currently people doing this seem to be getting rejected going on the reports I am seeing, forcing them to stick with the hub 3.0 or leave, neither of which is good.