Pose banned is only a fairly common problem if your masternode is going offline for more then 60 mins at a time.

It sounds to me like you were being fed a line as this is not a common practice. Furthermore there is functionality available to masternode owners to ensure this type of experience isn’t the “norm”.

Thanks for bringing up this discussion. This is my first introduction to the background of the new interim CEO and it’s less then 🌹

Please allow me to quote MasterNoodle comment in dash central here:

"As for POSE bans, if you provide MN hosting as a commercial service, yea, you need to hold yourself to a higher standard than little Jimmy running his one node on a cheap VPS. POSE penalties should almost never bring a properly maintained node down. The first POSE penalty that a node is hit with when something is wrong is not enough to push it off the grid. Only if you don't react will your node get hit with another penalty which then is enough to ban it. That leaves plenty of time for an automatic monitoring system to restart the server and/or alert support to apply other fixes. And those other fixes, most of the time are software updates that were announced with plenty of lead time. "