Virtual Server Fair Use Guidelines

Every Wlvhosting VPS and VDS plan falls under these Fair Use Guidelines, whose purpose is to ensure that performance stays reliable and even for each customer sharing our platform.

Categories of Service

VPS Services

Because Cloud VPS and Storage VPS plans run on shared infrastructure, they carry extra resource-usage controls and fair-usage rules that apply uniformly across this whole family of services.

VDS Services

Cloud VDS, Premium VDS, Performance VDS and Cloud ARM VDS plans are built on dedicated CPU resources. For that reason, running the CPU at full capacity around the clock is acceptable, provided that every network and abuse rule is properly observed.

CPU Usage

On VPS services, occasional or short-lived spikes in CPU usage are allowed when they stem from ordinary workloads and routine operations, for example:

• Hosting applications,

• Processing data,

• CI/CD pipelines,

• Compiling software,

• Running game servers,

• Performing backups.

That said, prolonged, excessive CPU consumption that harms other customers, undermines the stability of the shared infrastructure, or degrades general service quality may be treated as a breach of Wlvhosting' Fair Usage Policy.

Should such a breach occur, Wlvhosting retains the right to impose temporary CPU throttling on the workloads involved.

Shared CPU Resource Management

VPS services run on shared CPU infrastructure. To keep performance fair and even across the various virtualization nodes and customer workloads, mechanisms for CPU scheduling, balancing and performance normalization may be engaged on the fly.

During this process, CPU capacity on higher-performance nodes may from time to time be rebalanced so that the experience remains more predictable and uniform throughout the platform.

Because of this, certain virtual machines may now and then report CPU steal time as a normal side effect of shared resource management. Such steal time is not, by itself, a sign that the infrastructure is overloaded or that the host lacks sufficient resources.

Disk Resources

The maximum disk performance ceilings listed below are enforced:

Real-world performance can differ based on the nature of the workload and the total load on the infrastructure.

Network Throughput and Traffic

The bundled traffic can differ according to which server locations you pick. In the the USA and Hong Kong regions, allowances may be reduced because regional bandwidth there is more expensive.

Packets Per Second (PPS) Limits

To safeguard the stability of the infrastructure and to head off network abuse or DDoS-style traffic, automatic PPS caps are enforced on every Wlvhosting service.

A ceiling of roughly 200,000 packets per second (PPS) is set for each server, whether that traffic comes from a single connection or from many simultaneous ones.

Wlvhosting may automatically throttle and/or briefly isolate any workload producing abnormally high packet rates from the wider network, and a further review may be carried out for abuse-prevention reasons.

Prohibited Activities

Under this policy, the activities listed below are strictly forbidden:

• DDoS attacks and anything connected to them,

• Hosting or spreading malware,

• Phishing operations,

• Brute-force attacks,

• Running open proxy services,

• Operating public Tor exit nodes,

• Mining cryptocurrency,

• Sending bulk unsolicited email (spam),

• Anything that breaks applicable laws or regulations.

Torrent traffic on its own is not banned; even so, Wlvhosting reminds customers that the user bears full responsibility and liability for whether the distributed content is lawful, along with every abuse report tied to their services.

SMTP services may be used, provided the anti-spam, abuse and reputation rules are respected.

Service Restrictions

To preserve infrastructure stability and service quality for everyone, Wlvhosting keeps the right to impose temporary or permanent service restrictions whenever it is warranted. Measures that may be applied in such situations include:

• Throttling the CPU,

• Rate-limiting the network,

• Restricting SMTP,

• Putting temporary network protection in place,

• Suspending the service in abuse-related cases.