Site5 SSH Blockage: Safe but extremely inconvenient

I have been running some SVN repositories on a SIte5 server for some time and I can hardly complain about the service - it is generally stable and worth more than they charge for it. However, I am disappointed by the fact that they have disabled SSH access and plan to do so for at least a day because they are working on securing the setup. The reason is justifiable, but it leaves one wondering why they do not have a fallback feature that can provide SSH access to verifed client IP addresses to enable customers to continue operating hile they troubleshoot and correct the problem.

Instead of blocking all SSH-port 22 traffic, they should have alerted all customers that SSH was going to be blocked momentarily and then ask clients to login to the control panel and establish an IP range that can be allowed SSH access through the firewall. This would be a good balance between ensuring security, and allowing customers to continues ot access systems in the interim.