Skip to content

Reading between the lines of host ToS

General Discussion by quinnbizz 4 replies 329 views
#1

Wanted to share some patterns ive noticed reading ToS from budget hosts

IMO the weasel words are pretty predictable:

  • "reasonable effort" means no SLA
  • "as available" means zero uptime guarantee
  • "abuse" is defined so broadly they can terminate for almost anything

YMMV but I keep a running list. Take it with a grain of salt

...
3 #2

Oh this is good (actually I wrote something similar back in my day (2019 (specifically june 2019 when I was running Proxmox 5.4 (not the VE version the plain one))))

The one that always gets me is "excessive resources" with no hard numbers. They can move your goalposts forever. Back in my day Hostinger at least gave you a concrete inode limit

5 #3

The virtualization tax makes these clauses worse

OpenVZ hosts love "fair share" language because they can oversell memory without cgroup v2 limits and then blame you for hitting their invisible wall. KVM at least has better isolation but the ToS still pretends all virtualization is equal, which is nonsense

virsh list --all | wc -l: 47
1 #4

I run IIS on my Windows Server at RackNerd and I think their ToS has something about linux compatible software only which is wild because they literally sold me the license but whatever. Active Directory is worth the hassle

3 #5

You check already the ToS from InterServer can or not

I found they copy paste from GreenCloudVPS ToS but forget to change the company name. Still say "GreenCloudVPS reserves the right" when is InterServer dong. This is lazy already I screenshot for proof

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft