VPS Reviews & Impressions

Update: It keeps getting worse

Following the original CPU steal complaints, Servitro migrated my VPS to another host node. CPU steal appeared to improve substantially after the migration. Unfortunately, the migration introduced new problems.

First, SSH access failed following the migration, requiring troubleshooting through the VNC console. After restoring access, I discovered that public IPv6 connectivity was completely broken.

I investigated and captured network traffic showing that the configured IPv6 gateway was not responding to Neighbor Discovery requests. IPv4 was still working at that point, so I restored an affected DN42 BGP peering session by switching its WireGuard transport to IPv4.

I reported the IPv6 failure to Servitro support.

Then the situation got substantially worse.

Later on October 19, the VPS stopped responding over public IPv4 as well. The VNC console also stopped connecting, leaving me unable to access the server through either the network or the provider's console.

The control panel reported 0% CPU utilization, unavailable memory information, and zero network traffic. Although the service continued to be listed as Active, I could not determine whether the virtual machine was running.

At 12:10 PM on October 19, I attempted to start the VPS using the control panel's Boot function. The operation was cancelled after approximately 20 seconds with this message:

The system failed to respond to the action request. Further attempts are likely to be cancelled until the system is responding normally. Try again in five minutes.

This suggests a possible problem with the host or VPS management infrastructure. I cannot independently confirm the cause without access to the hypervisor.

I escalated the complete outage through support. As of this update, the VPS remains inaccessible, and I have not received an explanation or estimated restoration time.

I originally purchased this VPS to diversify my infrastructure across independent hosting providers and improve redundancy. Instead, I have spent days troubleshooting a service that was supposed to provide an additional reliable network location.

My conclusion

Cheap VPS hosting inevitably involves shared resources, and a single overloaded host would not by itself make me write off a provider. Infrastructure problems happen.

What changed my opinion was the combination of severe, persistent host contention, inadequate communication, and further failures following the host migration. What started as a performance issue progressed to broken IPv6 connectivity and eventually a completely inaccessible VPS.

I have encountered provider-side networking problems with other inexpensive VPS providers where support acknowledged the issue within minutes and began investigating. Problems are inevitable; how a provider responds is a major part of the service.

I understand that budget VPS hosting does not include enterprise-level support. However, expecting timely acknowledgment of an unusable service and meaningful updates during a complete outage is not unreasonable.

I will not be renewing my service with Servitro. The low price simply is not worth the instability, repeated troubleshooting, and lack of timely communication.

Based on this experience, I do not recommend Servitro for workloads where predictable performance, availability, or timely support matters.