All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
DeluxHost X-3
Hello LET,
this is my first review on LET, for https://lowendtalk.com/discussion/203848/deluxhost-net-high-performance-pre-order-new-vps-deals-start-7-annual-ned/p1 (Offer X-3)
I bought
They delivered it faster than advertised 14 days
After that, everything worked fine for a first few months
But yesterday, I started using the CPU heavily.
For a few hours, it worked just fine.
But then, the server was down!
Got an e-mail saying:
This is a notification that your service has now been suspended. The details of this suspension are below: ........ Suspension Reason: FUP Violation (CPU Usage) Please contact us as soon as possible to get your service reactivated.
WHAT THE FUCK!!
When I was buying this server, I have read all the ToS and FUP, and there was no thing such as Suspension FUP Violation, for using the CPU heavily
Before that, I received a kinda rude message saying: ToS change: Continued use of our services after this notice constitutes acceptance of the updated terms.
This is not legal! You can not change ToS in the middle of a billing period without consensual written consent.
After that, I opened a ticket, and got my server working, but they said that they will do it again for heavy CPU usage.
Tagging the provider: @DeluxHost
384.cz
Comments
Buy VDS or dedi.
Your requirement isnt suitable for vps and will impact neighbors unnecessarily
Okay, but throtting is appropriate, sudden FUP change and suspension is not and it is
misleading customers or using ethically questionable practices that may result in financial loss to customer(citing the selling rules).What VDS you recommend?
EDIT: Do not troll, please. This wasn't funny
I don't use VDS so I don't know what is popular in the market is.
I use VPS but I throttle the CPU by myself to 60-65%. Most provider doesn't mind in that range according to my experience.
You shouldnt expect real cpu usage for those 12$ annualy vps.
How is your "heavy CPU usage" ? 100% all core for hour ?
I have no problem with throttling!!
I think you misunderstand the way terms work. Most companies will have terms that can be updated at any time with little or no notice.
If you dont agree you can leave that is the option available to you.
100% legal.
generally unless its a VDS, you need to manage CPU usage by yourself.
however in deluxehost case, I'm surprised as their GB score is lower than usual, i assumed its already throttled to manage contention ratio.
Then what stops a provider from saying "You can use your server only under the full moon. We will delete all of your data otherwise"
Absolutely nothing. Terms are there to be read. 99.9% of people never read them.
Do you know what % of the CPU you were using (average of the 2 cores)?
Probably 90% one core and 7% the other
Nothing really. If you don’t like the full moon rule, you're free to switch to another provider.
Terms of Service can change at any time, and stating that continued use means you consent is standard practice.
Facebook, Discord, Google, AWS, they've all updated their TOS many times, and I've never had to give written consent or manually confirm anything.
It's always something like, "Starting from 31.02.2030, our new TOS will apply."
So that's like ~50% which doesn't seem outrageous but they have had issues with abuse in the past causing neighbor VPS's to not work well so I guess they had to get stricter.
I've seen a provider, i think big one, maybe AWS lightsail or something, give you some sort of CPU burst "credit". When you don't use the CPU much, you accumulate credit, and when you need to use the CPU heavily, you use your credit. When no more credit, the CPU is throttled. I could see the "credit" build up in the console. I liked that more than "fair usage which depends on your use case so we won't tell you what fair usage means".
But yeah, get a kimsufi and forget about all this.
Of course you did....or did you read it after they suspended the server!
Reality bites. If you wish to pay $12/year you are not going to be able to hammer the cpu regardless of what you believe you can do.
You get what you pay for.
This is a 12/year vps and you need to apply some common sense. Generally, best if you ask the provider directly what the cpu usage policy is before you make a purchase. Some will allow heavy usage for hours and others will not; pricing should usually be a good indicator for this.
Actually in EU it's not legal at all. In this case the old TOS is valid. Service provider needs to notify the customer of such change and give either an option to opt-out or cancel the contract. If the contract is month to month this also applies when the contract renews for the next month and continuing to use the service does not mean consent to new terms. There should be reasonable time for the customer to opt-out or cancel and usually you will get a notice few moths before the terms change.
Actually, in the EU or anywhere else if it is a clause in the tos then they can do it immediately and its something that you have already agreed to.
Considering the OP says it was read then they would know.
The law takes precedence over the TOS and if there's such a clause in the TOS it's considered invalid.
Hello @384_cz
I just want to clarify a few things personally.
In the last few months we’ve unfortunately seen a lot of real CPU and I/O abuse on some of our nodes, people running processes at full load 24/7, which caused serious slowdowns for others. Because of that, we’ve had to suspend hundreds of services to keep the nodes stable. It’s not something we enjoy doing, but we have to protect the honest users who use their VPS responsibly and expect fair performance.
That’s why our policy on resource usage is strict. When our monitoring detects sustained high usage, it triggers a review, it’s not an automatic or permanent ban, just a protection step. As in your case, once you opened the ticket and we checked the situation, the VPS was reactivated. We always give a second chance, and we prefer to explain things rather than simply terminate services.
This isn’t a criticism toward you, of course, we just apply the same rules to everyone to keep things fair.
The limits on excessive CPU and Disk I/O usage have always been part of our ToS (9.4–9.5); the latest update only made that section clearer, under EU rules, customers must be notified when a change substantially affects their rights or obligations. However, minor updates, like grammar corrections or clearer explanations of existing terms, don’t require formal consent.
If you’d like, feel free to PM me or share your ticket ID, I’ll be happy to check again personally and see what we can do.
Good luck with that.
No luck needed. If such a clause would be valid then anyone could use it to bypass their legal obligations and the law would be completely useless.
Not entirely true.
Laws on this vary from country to country and from contract type. Is it a business to consumer contract or business to business.
SUE them.
My post clearly talks about EU law. True, B2B contracts are more flexible. I hope OP is not running his business on a 12/year vps.
Would you be surprised by that? I bet plenty here are running clients on such!!
EDIT: Removed nonsense
Is suspending any better than severe throtting?
Going to court is probably the next adequate decision after the VPS is blocked. Personally, the server was also blocked for me. A telegram bot using PostgreSQL was installed on it, which practically did not consume server resources by more than 50%. After correspondence with support and as an exception, they allowed to reinstall the system and told me to control the resources. Personally, I made a strong-willed decision to transfer all my projects from DLX to other VPS and as soon as the server rental period ends (I have a lot of them) to leave DLX permanently. Just my couple of Cents
usually our first step is to pause or suspend temporarily, check what’s going on, and then reactivate the service once we’ve clarified the situation.
It’s not meant to be a punishment, it’s just a way to protect everyone quickly and avoid bigger problems on the node.