A Note About Vultr's Terms of Service
vultr.com
vultr.com
After getting invoice from car mechanic, a client goes over itemized list of parts and work, and in the middle sees an item called "it didn't fly - 10000". Client asks mechanic "What is this "it didn't fly" thing?". Mechanic sighs and says "Oh, well, it didn't fly. Removing.".
I'd love to know what did in that ToS though.
I think cloud providers (maybe all services really) should be required to provide some amount of notice of changes which the user will lose access to their data without accepting. Also would be really nice when providing said notice if they also included a diff from the last version the user had already accepted.
This kind of behavior should be illegal. They're holding your property (data) hostage.
Just a few weeks ago, one of my clients had their Vultr account suddenly suspended, within minutes of receiving multiple unexpected and mutually contradictory invoices that seemed to indicate some sort of billing error on Vultr's part. The client tried to resolve the issue with customer support, but that went nowhere because from Vultr's point of view, they no longer had an account with Vultr. Catch-22.
Luckily, the client had heeded my recommendation to keep backups with a different provider in a different location. So after a brief consultation we decided, "fuck Vultr," and proceeded to restore our cluster elsewhere. Now I'm making sure that none of my other clients have any part of their infrastructure dependent on this joke of a VPS company.
What if a law changes that requires them to update their ToS and would make it illegal to provide service to foreign nationals without including it? I guess they should provide a data exit path at least.