It could be the latency for which the hub 3.0 was notorious for. This was partly fixed with a firmware upgrade last year, but a proper solution could not be found as the Puma 6 chipset is rather weak. Having said that, posting some stats and logs could be be helpful.
Thanks for bringing this to our attention. Sorry that you've noticed some latency and packet loss since your upgrade.
I'm afraid this one's got me pretty stumped. All your stats look great from our end, too and I've had a look at the network segment but can't identify any problems there either. I'll flag this with another colleague to investigate further and see if we can come up with any ideas or suggestions.
Thanks for the suggestion. I'm currently running WS to monitor a little box that's running some suspect software. I'll see if I can run that check concurrently. I'm guessing that if the packet loss is in the upstream that points to a Hub3 problem. Is that right?
In the meantime here is yesterday's trace, with its strange 30 minute hump. And possibly a second one later.