All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Overselling, and when the customer discovers the issue, the response is like this =))
tiendungdev
Member
Everyone should check their VPS; your provider might be doing the same thing I'm experiencing.
Overselling, and when the customer discovers the issue, the response is like this 
)
Thank you for reaching out, and for your patience.
You're right, and we won't pretend otherwise: performance on our Singapore node isn't where it should be right now. The node is carrying a high number of VMs, many of them small, and at peak times that contention is noticeably affecting performance.
Normally we'd solve this by deploying additional hardware. Unfortunately, the current hardware supply situation has made that impossible for us in Singapore right now. Prices and availability for servers and components have become extremely tight across the industry, and we simply can't add capacity there for now. We're keeping a close eye on it and will expand as soon as it becomes feasible.
We know this isn't the answer you were hoping for, and we're sorry. It's frustrating for us too, and we'd much rather tell you a fix is on the way.
If the service in its current state doesn't meet your needs, just let us know. We're happy to refund your most recent payment if you find the service unusable for your workload.
Thanks again for your understanding, and please don't hesitate to reach out with any questions.
https://prnt.sc/nmYINrY95fTL
https://prnt.sc/Fvt1lC4ufX_I
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda4) before
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda4):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 520.47 MB/s (130.1k) | 902.73 MB/s (14.1k)
Write | 521.84 MB/s (130.4k) | 907.49 MB/s (14.1k)
Total | 1.04 GB/s (260.5k) | 1.81 GB/s (28.2k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 861.24 MB/s (1.6k) | 849.90 MB/s (829)
Write | 907.00 MB/s (1.7k) | 906.50 MB/s (885)
Total | 1.76 GB/s (3.4k) | 1.75 GB/s (1.7k)
AFTER
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda4):
Block Size 4k (IOPS) 64k (IOPS)
Read 38.15 MB/s (9.3k) 175.25 MB/s (2.6k)
Write 38.24 MB/s (9.3k) 176.18 MB/s (2.6k)
Total 76.40 MB/s (18.6k) 351.44 MB/s (5.3k)
Block Size 512k (IOPS) 1m (IOPS)
------ --- ---- ---- ----
Read 167.54 MB/s (319) 169.50 MB/s (161)
Write 176.44 MB/s (336) 180.79 MB/s (172)
Total 343.98 MB/s (655) 350.29 MB/s (333)
Comments
Still looks very usable depending on what you're trying to do with it.
Meh, how much are you paying? The performance is still probably fine for like 95% of use cases based on what you shared. But if a company gave me a fully AI generated reply I'd immediately start moving stuff off either way lol.
It still look good and not that bad also they did offered you refund which many don't offer.
Still looks okay for a VPS to me at least. VPS means sharing the hardware with others in the node, not dedicated to you. If you can't accept this kind of slowdown, get a dedi.
It's good...
First, I apologize to everyone reading this for the lengthy reply.
Hi @tiendungdev !
You're welcome to tag us in the post if you have an issue, and if the ticket response is unsatisfactory, please state that in the same ticket.
Your VPS is in Singapore, and it's been a sold-out location for a while, yet we continue to receive deployment requests, all of which we decline.
None of our nodes are oversold. We publicly shared the formula through which we determine how many VMs are hosted on a node:
Node Total RAM minus 8 GB RAM = Total RAM available for VM deployments.
Example: 192 - 8 = 184 GB available for VMs, and we fill nodes based on that.
As the ticket states, Singapore is currently pretty full, and there is no other node to move you to; we also offered a refund for your last payment if the performance does not meet your standards. We also state publicly that performance fluctuates as nodes fill up.
Is this performance ideal? Absolutely not. Do we want to do something about it? Yes, we do. However, the hardware market is horrible, and Singapore has been a hot location. I told other customers this, and John did the same. We want to improve things, but our hands are tied, and the only thing we can do right now is either:
For what it's worth, we are offering these refunds outside our refund policy, and we process them immediately if the customer accepts, without any delay whatsoever. If the response comes in during off hours, we process the refund first thing the next morning. We've even refunded "Funds" which customers added to their accounts. Why? Because I don't want someone's money when they are not happy with the service they received, and we don't want to keep the $10, $20, or even $100 paid for the service if the customer is suddenly unhappy. Even if you paid a year in advance, we'd refund your remaining balance, including the month you became unhappy with the service. This is why we don't offer annual billing for VPS plans.
We cannot and will not claim things are honky dory when they aren't, and we have never done so when we received complaints. We always take action and do what we can.
From this post, I understand you're unhappy with the performance and seem indifferent to the refund offer. To be completely honest, I'm not entirely sure how we can make this right.
Furthermore, we never claimed we had a solution in place, and we have been fully transparent about the situation.
The response is not fully AI-generated. We use an AI Assistant tool that can reformulate a response or generate one based on the conversation and past cases; then the person posting the response edits it as they see fit.
We are also testing automated AI-agent ticket responses, which are signed by the AI agent and clearly state that an "AI Assistant" is posting the response.
The staff and I also review those responses, and if something is inaccurate, we correct it in the next response and own the mistake.
Some of these responses are predefined because we receive the same inquiry repeatedly, and it makes little sense to write the same response by hand over and over.
We also use Grammarly to check response tone and help ensure responses aren't accidentally passive-aggressive or unprofessional. In fact, I ran this response through Grammarly both as I wrote it and after, and I am not hiding that.
If anyone has a question or needs additional clarity, feel free to tag me here in this post, or on Discord.
Just because you don't oversell RAM doesn't mean you don't oversell the other resources lol? or what am I missing?
Before I read any of that, what are you paying for the server?
exactly, tho wouldnt really complain on mild cpu overselling but if you dont use thicc-provisoning then get outttt
You're not missing anything; I'm the one who missed mentioning that we are also restricted by the disk size. For example, the node has 3.5 TB available for VMs, and the disk size limitation comes before RAM. But to be honest, if either of the limits is met, the node will not accept new VM deployments, period.
We set a hard limit in VirtFusion on the total disk usage on the node based on the available storage.
CPU? There are only so many vCores, and unless someone is paying for dedicated CPU, each user gets a set number of cores. If we limit the number of VMs to the number of Cores, that's dedicated CPU and a completely different product at a completely different price point.
VirtFusion, AFAIK, does not offer thick provisioning for disks. However, we are restricting the total disk size for all VMs.
overlay proxmox for the go
My man, click the screenshot in OPs thread, it's literally copy and paste AI response.
It's OK, some people are fine with it.
What happened to @Snitchboss123, @angstrom ?
The stats for $3/mo is fine BUT they are being advertised as "High-performance AMD Ryzen & EPYC KVM VPS with blazing NVMe storage" The speeds are fine for many use cases but they are not NVMe speeds. Provider has oversold versus what they advertised.
Ban evasion
(Though it wasn't me who banned them)
Hopefully, no one will miss them
that's clearly human text and corrected with grammarly, the response is 10/10