Yes, the cloud editor is still using the hub's cloud connection to go into your hub and pull the piston data off of it. So it appears you have an actual problem with Webcore, that you would also see if you were locally on the hub.
I would try rebooting the hub remotely, since you have remote admin. It would not be a bad a idea to also do the rebuild database option on your reboot, selected on the options when rebooting. Apparently it is suggested to let the hub "settle" for a few minutes after the reboot before loading Webcore.
Looks like the final solution in that thread was to reboot their router. Not sure if you have access to do that remotely, or if someone at the remote location could do it for you. You could also try rebooting the router at your house.
