New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Hello.
Order number #3434760943
I don't have bonus
Freebee for Order Nr. 3611898500 please
Don't hold your breath, there's no such thing as a free prize. I've had my server for two months now, and they still haven't sent out the prize
The freebies are delivered every day Sir.
I didn't get any either
Comment on page 3!
VM-x/AMD-V : ❌ Disabled
why is it disabled on the M series vps I just ordered? my previous M series vps had it
YABS for M-4 VPS
Kinda disappointing. My other M-4 VPS with a 9950x has better GB scores and VM-x/AMD-V enabled.
But at least the disk speed seems to be much better lol
Hello,
I'm really satisfied with your service and pricing, but even though I understand your policy of reducing the number of tickets per customer, I think the current limitation is too restrictive given the current response times. I opened an informational ticket for a fairly trivial question on Tuesday with low priority, and to date I have not yet received a response. As a result, I am unable to open new tickets for a technical request on the VPS.
Ticket #JPN-195171
Answered, sorry for the delay!
Hello,
I get the comparison with your other node, but on the 7950X3D we had to disable AMD-V (nested virtualization) because it was causing instability on the host.
This isn’t something we “decided for fun”, it was disabled to keep the node stable. The 9950X doesn’t show the same behavior, which is why AMD-V can stay enabled there.
About your benchmarks, they’re completely normal for a shared 3 vCPU VPS on this kind of CPU. Nothing looks throttled or artificially limited. Disk performance is actually good, and network results are solid too. There’s nothing wrong with those numbers.
If you specifically need nested virtualization for your workload, we can look at moving you to a node that supports it. If your usage is typical (web services, apps, bots, etc.), you won’t see any real-world difference in performance.
Does it support dcma ignore 🤔?
Please send freebie for Order ID # 2288750449.
order 9972716480
Could I get an extra vcore please?
订单号3382048957
+1 GB RAM谢谢
I misspoke; I don't need Vcore. If possible, please increase my storage space.
TL;DR: Do not recommend. 79% uptime over the last 30 days. Support puts tickets on hold instead of actually resolving anything.
I've been dealing with persistent network issues on my DeluxHost VPS since mid-December 2025. Here's how it's been going:
The network is fundamentally unreliable. MTR reports consistently show 92-99% packet loss within their own network infrastructure. Not on my end, not my ISP, inside their backbone. The server becomes completely unreachable for days at a time. My Hyperping monitoring shows 79% uptime over the last 30 days. Even from Amsterdam, where their datacenter is located, the IP is frequently unreachable.
Support "resolution" is a loop of the same steps that don't work:
1. "Send MTR" → I send MTR showing packet loss in their network
2. Silence for days
3. "We applied some changes, can you check?" → Still broken
4. IP change → New IP, same problem
5. OS reinstall → Worked for 2-3 days, then broke again
6. Back to step 1
This cycle has been going on for two months now.
The current situation: The server has been completely down for over 6 days straight. Instead of responding to the ticket, support simply put it on hold. Again. No update, no ETA, no acknowledgment. Just silence.
I've suggested reasonable alternatives: migrating to a different host node, assigning an IP from a different subnet, moving to a different datacenter location. All ignored. The only tool in their toolbox appears to be "send MTR" and "we applied some changes."
Bottom line: If you're considering DeluxHost, think twice. And then think again. A VPS that's unreachable 20%+ of the time and a support team that responds to outage tickets by putting them on hold is not a service, it's a liability.
I'm sorry you're experiencing these issues, but honestly, I feel like they don't reflect reality.
Uptime is currently stable and without any particular problems.
Individual cases like yours may have longer response times due to the response times coming from our Upstream, to which we send the MTRs.
The network is not 100% managed by us. We are customers ourselves, and so if your ticket has been put on hold, it's not to mock you, but because we too are waiting, Putting a ticket on hold does not mean ignoring it.
We always do our best to resolve issues as quickly as possible.
I'll conclude by saying that most of our customers are happy and satisfied with our services.
Thanks for the response.
Anyone can try pinging the IP visible on the screenshot. It's been down for 6+ days. The server itself is fine, I can access it via VNC, so it's not a server issue, it's your network.
I understand you depend on your upstream. But two months is not a "longer response time", it's an unresolved issue. And when the ticket gets put on hold with zero communication for days, I have no way to know if you're waiting on upstream or just forgot about it. A simple "we're waiting on upstream, no update yet" would go a long way.
From the customer's perspective, when the server is down for 6 days and the only thing that happens is the ticket silently goes on hold with no message, it absolutely feels like ignoring it.
#KNL-957226
I don't doubt that. But as I mentioned in my ticket, there are apparently only two clients affected by this routing issue. If the problem is that narrow, surely there's a more targeted solution than running the same MTR/IP change/reinstall loop for two months? I've suggested alternatives (different host node, different subnet, different DC). None were addressed.
I'm not writing this to bash you. I genuinely want the service to work. But at this point I've paid for two months of a server that's been usable maybe 79% of the time, and right now it's been completely dead for almost a week.
I'll review your ticket and tell you exactly what we can do to help now, no problem, we can solve all.
In that case, could I receive a refund please? Not only am I disappointed with the performance, but your network too. Yesterday my windows rdp connection cut off 4 times due to that. I’ve made a ticket yesterday, and am waiting for a response.
PYJ-661251
We'll look into your ticket, there are no issues with that.
But we stand by our opinion. We don't see any problems on that node and from your benchmarks.
Any other issues could have been resolved of course.
We hope to see you again in the future!
Invoice #20016
+1 vCore if possible
In the Post said The N series are Instant Delivery!
but after paying the invoice, it says Status -> Pending and its been hours!
maybe i dont understand what Instant means anymore!
Let me check this, the server Should be instant delivery sir.
Hello. How do I view the order number? I only see the invoice in my personal account.
You must look for the email that has as subject "Order Confirmation"
Hello.
Order Number: 1366845046
Could I get an extra vcore please?
Still checking ?
Order Number: 2886192190
Invoice #20016
Order Number: 2269093043
It has been 5 hours in the process of deploying the server. Port upgrade up to 10G, please. Thanks!