Fair Usage Policy
Last Updated: February 12, 2026
1. Introduction
1.1. This Fair Usage Policy (hereinafter referred to as the "Policy" or "FUP") defines the technical standards and acceptable limits for the use of infrastructure resources provided by ONLINE CONNECT LTD, operating under the trade name HOSTOFF.NET (hereinafter referred to as the "Provider", "Company" or "Executor").
1.2. This Policy is an integral part of the Terms of Service (hereinafter referred to as "TOS") published on the hostoff.net website. The Policy specifies and supplements the TOS provisions regarding technical resource consumption standards.
1.3. The list of prohibited activities and general acceptable use conditions are established in Section 5.3 of the TOS. This Policy does not repeat them but establishes quantitative and technical criteria for acceptable resource consumption.
1.4. By using the Company's services, the Client confirms that they are familiar with this Policy and undertakes to comply with it.
2. Network Traffic and Bandwidth
2.1. Traffic Accounting
2.1.1. The volume and conditions for providing network traffic are determined by the Client's tariff plan.
2.1.2. Traffic is accounted for as the total volume of incoming and outgoing data (in + out), unless otherwise specified in the terms of a particular tariff plan.
2.1.3. The traffic consumption accounting period begins from the service activation date (or the date of the next renewal) and ends upon expiration of the paid period. The traffic counter is reset at the beginning of each new accounting period.
2.2. Fixed Traffic Volume Plans
2.2.1. Upon reaching the traffic limit established by the tariff plan, the Provider has the right to:
- a) limit the network connection speed to 10 Mbps;
- b) suspend data transmission until the beginning of a new accounting period;
- c) offer the Client to purchase additional traffic volume.
2.2.2. The cost of additional traffic is determined by the current tariffs published on the hostoff.net website.
2.3. Unmetered Traffic Plans
2.3.1. Tariff plans designated as "unlimited traffic", "unmetered traffic" or "unmetered" provide traffic without a fixed volume limit, however within the bandwidth specified in the tariff plan.
2.3.2. The network port speed specified in the tariff plan (e.g., 100 Mbps, 1 Gbps) is the maximum technical connection speed.
2.3.3. Systematic use of bandwidth at a level exceeding 80% of port capacity on average for a period exceeding 30 minutes, negatively affecting the quality of service for other users, is grounds for applying measures described in Section 6 of this Policy.
Actual data transfer speed depends on:
- network channel and route congestion;
- geographical location of source and destination;
- technical characteristics of intermediate operator equipment;
- overall load on the Provider's infrastructure.
2.4. SMTP Port Restrictions
2.4.1. Outgoing connections on ports 25, 465, and 587 (SMTP) are blocked by default on all servers.
2.4.2. Access to the specified ports may be opened upon Client request through the support ticket system after verification and internal review of the application.
2.4.3. The Provider has the right to restrict or revoke access to SMTP ports at any time upon detection of abuse.
3. Computing Resources (CPU and RAM)
3.1. Resource Nature
3.1.1. vCPU and RAM resources in virtual environments are shared resources of the physical host node and are distributed among multiple users.
3.1.2. vCPU and RAM characteristics specified in virtual server tariff plans determine the maximum available resource volume for peak loads but do not guarantee constant availability at 100% load in continuous mode.
3.1.3. Guaranteed allocation of CPU and RAM resources in full volume is provided only on dedicated servers.
3.2. Acceptable Usage Limits
3.2.1. Short-term peak CPU loads (request processing, compilation, task execution, etc.) are a normal operating mode and are not restricted.
3.2.2. Acceptable usage is considered when the average vCPU load does not exceed 70% of allocated cores during a continuous period exceeding 60 minutes.
3.2.3. Maintaining vCPU load at 100% or close to 100% for extended periods is grounds for applying measures described in Section 6 of this Policy.
3.3. Additional Restrictions
- 3.3.1. Cryptocurrency mining on virtual servers is permitted only with prior written approval from the Provider.
- 3.3.2. Running performance stress tests (benchmarks) in continuous mode is not permitted.
- 3.3.3. Use of scripts, processes, or mechanisms aimed at bypassing the fair resource distribution system is prohibited.
3.4. Recommendations
3.4.1. For workloads requiring consistently high CPU performance, the Client is recommended to:
- upgrade to a tariff plan with dedicated resources;
- consider renting a dedicated server;
- contact support for optimal solution selection.
4. Disk Subsystem and I/O Operations (IOPS)
4.1. Resource Nature
4.1.1. The disk infrastructure of virtual servers is shared storage. Excessive load on the disk subsystem by one user can negatively affect the performance of other users on the same physical node.
4.2. Restrictions
4.2.1. Not permitted:
- a) continuous intensive read/write operations creating excessive load on the disk subsystem for extended periods;
- b) conducting continuous disk subsystem stress tests (fio, dd, bonnie++ and similar in long-term testing mode);
- c) using VPS exclusively as file storage without active use of computing resources, unless provided for by the tariff plan.
4.2.2. Detection of excessive load on the disk subsystem is grounds for applying measures described in Section 6 of this Policy, including IOPS throttling.
5. Monitoring
5.1. The Provider monitors resource consumption to ensure compliance with this Policy and maintain infrastructure stability.
5.2. Monitoring is aimed at analyzing:
- CPU, RAM, IOPS consumption levels;
- network traffic volume and nature;
- anomalous behavior indicators.
5.3. Monitoring is not aimed at analyzing data content or personal information stored on Client servers.
6. Violation Response Procedures
6.1. This section defines the procedure for responding to violations of resource consumption standards established in Sections 2-4 of this Policy. The procedure for responding to violations of acceptable use conditions (abuse, prohibited activities) is defined in Section 5.3.2 of the TOS.
6.2. Notification
6.2.1. Upon detection of exceeding acceptable resource consumption limits, the Provider notifies the Client through the support ticket system with a description of the violation nature and recommendations for its elimination.
6.3. Remediation Period
6.3.1. The Client is provided with a reasonable period to eliminate the violation:
- up to 24 hours — for violations negatively affecting infrastructure or other users (systematic excessive CPU consumption, exceeding acceptable disk subsystem load, exceeding bandwidth limits);
- up to 72 hours — for violations not having significant impact (episodic exceeding of recommended levels, resource use not in accordance with the tariff plan purpose).
6.4. Immediate Restriction Without Prior Notice
6.4.1. The Provider has the right to restrict resources or suspend service without prior notice in cases where resource consumption:
- a) creates a direct threat to the stability of the physical host node;
- b) causes performance degradation for other users requiring immediate intervention;
- c) is related to a network attack originating from or directed at the Client's service.
In such cases, the Client is notified after the fact through the support ticket system.
6.5. Escalation
6.5.1. Failure to eliminate the violation within the specified period, as well as repeated violations, may lead to:
- a) application of resource throttling;
- b) temporary suspension of service provision;
- c) termination of service provision in the manner established by Section 8 of the TOS.
6.6. Appeals
6.6.1. If the Client believes that the restriction was applied erroneously, they have the right to file an appeal through the support ticket system. The decision is made by the Provider based on the results of an internal review.
7. Policy Changes
7.1. This Policy may be updated or modified at any time to reflect operational, technical, or regulatory changes.
7.2. The current version of the Policy is available at: hostoff.net/fair-usage-policy
7.3. Clients are notified of significant Policy changes through the control panel and/or email specified during registration.
7.4. Continued use of services after publication of the updated Policy is considered acceptance of the modified terms.
HOSTOFF.NET