Formatting is fine, exactly how we like it!
Rather too many T3 errors on the upstream counts, and a small but suspicious blip of post-RS counts on downstream channels 12 and 22. Coupled with high (although within range) upstream power, my suspicion is an upstream noise problem. But from what I see so far, I can't offer any definitive view; if you wait (sometimes a day or two) for the forum staff to take a look they can advise, as they can see more data that the logs show you or I. You could also post up the Network log - that sometimes shows clearer evidence of connection faults.
Be persistent if the advice is "looks good from our side" - sometimes the diagnostics VM use miss things, and there's a tendency to come out with irrelevant comments like "you've got a wifi device too close to the hub".
Always worth undoing, wiping and remaking all coax cable connectors (if you're careful, including in the brown plastic Omnibox mounted on the outside wall), making sure all hub power leads are fully pushed home, and also trying a pinhole reset. Common opinion here is that it requires a good push-and-hold for 30 seconds to properly force a reset, and you may need to hunt around for something suitable to both get far enough into the hole and push the contact down. Sometimes that cures the problem, sometimes it'll need a technician visit. If your hub and the connection are all working as you pay for, you should not be having to regularly reconnect devices to the hub (although any "smart" devices that need manual reconnection when connectivity is briefly lost are also to blame - if that's the case, poorly conceived techno-tat, the equivalent of needing to fiddle under the bonnet to reset a car's control unit if it stalls).
One other thought - you don't have a Dell laptop with an Intel Killer wifi adaptor do you? There's been many reports of those triggering reboots of VM hubs.
