All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Linveo.com: The Customer Loyalty Trap—Massive Performance Decline, Unresponsive Support, and Unjusti
I have been a customer of Linveo.com for over a year and have purchased a substantial volume of services, having had 150 VPS instances with them. My business depended on their infrastructure. While initial service was acceptable, the handling of a recent critical issue demonstrates a complete collapse in their service quality and customer care. Potential buyers, especially those looking for reliable, high-performance hosting, need to be aware of this deterioration.
The Incident: From Working Well to Unacceptable Performance
The problem began with a recently purchased Intel KVM VPS 16GB (Ohio). It was operating fine until November 1, 2025, when the main node failed, forcing my VPS to be migrated (Ticket ID: 23405).
The post-migration performance was a disaster. The new node delivered extremely poor disk IOPS, rendering the server virtually unusable for a database-driven application:
Metric
Result
Read
42.21 MB/s
Write
42.30 MB/s
Total IO
84.51 MB/s
For a modern VPS utilizing SSDs, these numbers are abysmal and completely unacceptable. This drastically low I/O immediately led to severe performance issues with my MariaDB database, confirming a disk I/O bottleneck.
The Support & Blame Game
When I raised a ticket to address the slow IO, Linveo’s support was dismissive and ultimately accusatory.
Stage 1: Dismissal
In response to the low IOPS figures, support stated, "We have reviewed your issue and there is nothing here that indicates there is bad performance with disk IO. Those results are in range and will vary since it is a shared service."
This reply is highly concerning. It shows either a profound lack of technical understanding regarding acceptable IO performance or a deliberate attempt to downplay a major infrastructure issue. Any experienced user knows that performance in the 40MB/s range will cripple most modern applications.
Stage 2: Throttling and Blame
After I explained how the low IO was directly affecting my MariaDB queries, their next response was to shift the blame entirely to me:
"Your VPS has been throttled for a while due to it constantly exceeding 50% of CPU usage for extended periods of time. If you want this throttle removed, then you will need to address the constant CPU utilization."
While running a typical WordPress site under WHM can be CPU-intensive, I use CloudLinux to monitor and limit resource consumption. The sudden and unannounced throttling, combined with their refusal to acknowledge the proven performance defect (the 42 MB/s IOPS), suggests the throttling was either unjustified or a punitive measure taken because I pressed them to fix their infrastructure problem.
Conclusion and Final Warning
After I refuted their throttling claim and provided my setup details, support stopped responding entirely. My request for a refund was ignored.
After investing heavily in Linveo services—purchasing 150 VPS instances over a year—I learned the hard way that loyalty means nothing when their infrastructure fails. They will deny clear performance issues and then resort to throttling your service and cutting off communication rather than addressing their own technical shortcomings.
Do not buy from Linveo.com if you require reliable performance or expect competent customer support. My experience shows that once you encounter a technical issue, you will be left with a useless, throttled VPS and zero recourse.
Comments
Another ai slop?
Ai Help me to Summarise - I just give the main Point
The plans are very budget, almost the same as Contabo, it's honestly no surprise as a host that you were throttled. CPU resources, especially ones that need to be utilized often, come at a premium. But if you have 150 VPS unless you were just cycling through cancellations/new orders, then surely something could have been done for you to avoid this problem.
If you need a large amount of VPS and don't want to manage the underlying hardware/virtualization I'd be happy to help and give you some isolated/private VPS environment where you just have the VPS and don't have to worry about anything else. I do this basically with my hybrid dedicated servers (albeit with a 1 server limit except for partners who use for business), and work with some people that run Wordpress-focused environments.
Good luck.
I've been using Linveo for a while (AMD line), and I remember they mentioned here that VPS's CPU usage should average around 30% or so.
P/S: It's in their AUP.
CPU Consumption: All KVM VPS plans include shared CPU cores. All of our customers are able to utilize 100% of their allocated CPU for short periods of time to run backups, compile software, run benchmarks, etc. Average CPU use for a VPS customer should be no more than 25%. Using more than 25% of your allocated CPU for a period longer than 1 hour is prohibited and is grounds for suspension or termination.any YABS?
I don’t believe that my VPS has been using 100% CPU for an extended period.
`Uptime : 2 days, 18 hours, 32 minutes
Processor : Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz
CPU cores : 6 @ 2194.842 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 15.6 GiB
Swap : 1.5 GiB
Disk : 103.8 GiB
Distro : CloudLinux 8.10 (Vladimir Aksyonov)
Kernel : 4.18.0-553.70.1.lve.el8.x86_64
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
ISP : LINVEO, LLC
ASN : AS62564 LINVEO, LLC
Host : LINVEO, LLC
Location : Grove City, Ohio (OH)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda4):
Block Size 4k (IOPS) 64k (IOPS)
Read 42.21 MB/s (10.5k) 395.84 MB/s (6.1k)
Write 42.30 MB/s (10.5k) 397.92 MB/s (6.2k)
Total 84.51 MB/s (21.1k) 793.77 MB/s (12.4k)
Block Size 512k (IOPS) 1m (IOPS)
------ --- ---- ---- ----
Read 452.96 MB/s (884) 479.12 MB/s (467)
Write 477.03 MB/s (931) 511.03 MB/s (499)
Total 930.00 MB/s (1.8k) 990.15 MB/s (966)
`
it looks reasonable, seems like its capped, cant tell whats the issue unless you show the historical RW IOPS
Similar story but continuous intermittent network problems with another provider.
The support kept telling me there was nothing wrong with the node network, ignoring the fact that multiple network monitoring systems detected inaccessibility.
Despite the fact that the performance and stability were acceptable most of the time, i had to cancel the renewal for more than a dozen 7950X VDS.
For Linveo, I reviewed the 8 tickets of last 2 years, most received a response within a few hours. When network and performance issues arose, they migrated the VPS to other regions, monitored and moved clients from one Node to another to free up performance.
i can confirm that performance (GB6) has dropped significantly in the last few days. see yabs.
the GB6 values were previously much higher, usually around 3000-33xx!
earlier this year: