Image

Help and description of the process of ordering services → DDOS attack protection service

[VPS/VDS servers]
Date of publication: 27.01.2023

Description of service

Traffic filtering is carried out automatically 24/7 based on the intelligent learning traffic filtering system Arbor (http://www.arbornetworks.com/).

Technical limitations of the service

Within 5 minutes from the start of the attack, the filtering system will begin recording data about the attack to generate a report.

The service provides traffic filtering only for a network segment using the IPv4 protocol.

In some cases, the Service may not provide complete protection of the Object from a DoS/DDoS attack or part thereof, including within an IP/MPLS network.

We have the right to refuse to redirect the Object's traffic to the Cleaning Device if this may lead to negative consequences for the functioning of the networks of RIPNET LLC and the equipment of other clients.

The Cleaning Device operates based on an analysis of the parameters of previous DDoS attacks or previously received unwanted traffic. From the point of view of preventing undesirable events, these parameters are probabilistic in nature. In this regard, RIPNET LLC does not guarantee that passing the client’s Internet traffic through the cleaning device will provide the level of protection against DDoS attacks expected by the client.

Price

When connecting to the service, the client is provided with a dedicated IP address, which is configured by our technical support on the client’s virtual dedicated server. This IP address is allocated from a protected subnet and it is this that must be used to configure a website or other service. The cost of the service is indicated for 1 IP address; if you need several protected IP addresses, please contact technical support. The service can only be activated when ordering a VPS / VDS server.

Note: The service provides protection against medium and large attacks; in case of small attacks designed to disable (freeze) services by exhausting server resources (for example, syn flood, bruteforce), we recommend setting up this protection on the server itself as described in our article: protecting the web server from flood attacks.