Agreed it does appear to be solved and I totally understand Remote Utilities frustration - this was not related to their company at all but at first one might think so - tell me exactly what to whitelist for my watchguard botnet detection and I will do so just in case a random thing like this happens again. I did try whitelisting id.remoteutilities.com but wasn't sure if anything else needed to also be whitelisted. Thanks for all your help - I'm sorry if I was frustrated with Remote Utilities!
We do our best to help as fast as we possibly can. However, this specific issue isn't a fault of Remote Utilities. It is an issue with WatchGuard Firewall/Firebox erroneously blocking our legitimate service (as reported by several different users/customers already).
Moreover, judging by a yesterday's tweet addressed to WatchGuard Remote Utilities isn't the only service that was affected.
We recommend that you as WatchGuard customers contact them too and ask for this issue to be resolved as quickly as possible.
Right except Watchguard claims the issue is resolved per the tweet....