Monitoring DDoS attacks with the Network Security Dashboard

Wissensdatenbanken

Monitoring DDoS attacks with the Network Security Dashboard


Icons/System/eye-open Created with Sketch. 6643 Ansichten 31.10.2025 Cloud / Dedicated Server (Bare Metal)

Objective

This guide explains the Network Security Dashboard and provides an overview of counter measures triggered by our DDoS protection infrastructure when malicious network activity is detected. You can find details on which additional protections should be implemented to keep your services up and running. Moreover, traffic charts are available on the dashboard for scrubbing centre activity periods to better visualize the situation.

Requirements

Instructions

Network security

OVHcloud's Anti-DDoS infrastructure is a multi-layered, distributed defense system to fight against cyber attacks. It consists of multiple edge locations and scrubbing centres that can analyse and clean up malicious traffic. Together with the Edge Network Firewall and the GAME DDoS protection, it offers quality protection services for various cases.

The Anti-DDoS infrastructure is constantly analysing incoming traffic (detection mechanism) and eventually redirects such traffic via our scrubbing centres (also known as “mitigation”) located in data centres around the world. Incoming traffic is then deeply analysed and eventually filtered out from malicious packets before reaching your server or service.

What happens when an attack reaches my service's IP?

Every time an attack is detected towards any IP of your service, you are notified via email that traffic has been rerouted through the Anti-DDoS infrastructure. You can also monitor these periods on the Network Security Dashboard with additional details.

During an attack, an active mitigation action will be indicated by a warning icon on the IP listing page (in the Manage IPs section of your Control Panel).

red-line-attack

Find more information on how DDoS mitigation is achieved at OVHcloud here.

Please note that the protection logic is based on public IP addresses associated with a server (or service). As a result, statistics and charts are displayed or calculated on a per-IP basis.

Network security notifications

red-line-attack

Log in to the OVHcloud Control Panel, open the Network menu in the left-hand sidebar and click Public IP Addresses. Ensure that Advanced mode is enabled to see the Anti-DDoS infrastructure status and its components configuration.

The columns correspond to the Anti-DDoS scrubbing (Mitigation) status, the Edge Network Firewall and GAME firewall features availability and their statuses.

  • The Mitigation state can be:

    • Automatic - The scrubbing centre is in automatic mode, and reroutes traffic for deeper analysis when needed.
    • Forced - This indicates the scrubbing centre is taking action right now.
  • The Firewall column indicates the state of the Edge Network Firewall which can be:

    • Enabled - Firewall is enabled for this IP.
    • Disabled - Firewall is disabled for this IP.
    • (no status) - Firewall configuration is not created. To configure rules, click on the ... button then select Create Firewall.
  • The GAME firewall (only available for OVHcloud Game dedicated servers) state can be:

    • On - The GAME DDoS protection is enabled on this IP.
    • Off - The GAME firewall is available but disabled on this IP.
    • (no status) - The GAME firewall is not available for this IP. This means the listed IP is not configured on a supported product range.
  • The Alerts column may indicate an active scrubbing centre with a warning icon and appropriate hint.

Network Security Dashboard

Log in to the OVHcloud Control Panel, open the Network menu in the left-hand sidebar and click Network Security Dashboard.

In the scrubbing centre log tab, you can retrieve all the information about attacks that were detected in the past (or that are ongoing).

red-line-attack

In the table, the following columns are present:

  • Detection time - Timestamp of the first attack detection
  • End time - Timestamp of when the scrubbing centre finished mitigating
  • Destination IP - The IP that was the target of the attack
  • Attack vectors - Provides information about detected types of attacks, such as UDP or TCP attack, etc.

The data retention period for scrubbing centre logs is 1 year.

Please note that source IP addresses for detected events are not displayed because they are usually spoofed (DDoS attacks may point to other sources than the ones really comes from) and such information would be misleading or not usable.

In the Traffic chart tab, you can see a graph showing traffic to your IP address (bps or pps).

red-line-attack

It presents malicious traffic that was dropped (in red) and clean traffic delivered to your IP address (in green). There are also basic mitigation statistics displayed, i.e.: how many attacks were detected for a selected IP, how much traffic (or packets) was cleaned during attacks or how many times scrubbing centres took an action to inspect your traffic (number of events) in a selected period of time.

The data retention period for the traffic chart is 2 months.

FAQ

Why do I see not all of the attacks on the Network Security Dashboard?

Depending on the nature of the attack, different actions may be taken to best eliminate the threat. In both cases attacks are best mitigated as close to the origin as possible:

  • In case of an attack coming into the OVHcloud network (external), traffic is redirected to the Anti-DDoS scrubbing centres for cleaning (thus visible on the Dashboard).
  • Please note that attacks originating from inside the OVHcloud network (internal) are managed by our security teams. Mitigation focuses on blocking the origin of the attack and will not be reported by Anti-DDoS infrastructure systems.

No data is displayed in scrubbing centre logs, is this normal?

Yes, it means that no suspected attacks have targeted your public IP addresses.

No traffic chart or data is shown for an IP address I enter.

Such data is available only for public IP addresses during automatic Anti-DDoS infrastructure detection events (when traffc is redirected via scrubbing centre).

The traffic chart for some positions in the scrubbing centre logs is not available.

Traffic chart data is available only for the past two months, while log entries can be reviewed for the past year.

An attack on my service is persisting, how can I better protect my server?

Some types of attacks may be so specific that our Anti-DDoS infrastructure will not be able to detect and clean it automatically. In such cases, the firewall configured on your server is your best option. We also recommend offloading some of the server firewall rules to the edge of our network - using the Edge network Firewall.

For more information how to configure Edge Network Firewall rules, please see our Edge Network Firewall guide.

My service is attacked and I experience problems on my server. What more can I do?

Anti-DDoS infrastructure is a solution designed for best efficiency and wide ranges of services to protect. In some specific cases, it may need additional tuning (e.g. for application specificity or size). To request this, please visit our Help Centre and search for the appropriate action inside the "network attack and/or Anti-DDoS related" category.

To let us better understand your case and to be able to help you, please provide us with some more details:

Step 1 - Capture traffic

In order to deliver the best solution for you, first we will need to analyse a traffic sample.

To provide us with such a capture, run this command on Linux:

tcpdump -w capture-ovh -c 100000 port not ssh

If you are using Windows, use Wireshark and capture 100000 packets.

Once the command finishes running, the capture file is created. You can either attach the created file to your support ticket or upload it to our file sharing solution using this guide.

Make sure to share the uploaded file's link with the support team in your ticket.

Step 2 - Provide OVHcloud with information

In any case where adjustments to our Anti-DDoS system will be necessary, it is mandatory to provide us the following specific details:

  • Service hosted on the server that is affected
  • Date and time of when the attack started
  • Date and time of when the attack finished
  • IP(s) affected
  • Service, protocol and port used by the affected service
  • Size of service (XS: 1-10, S: 10-100, M: 100-1k, L: 1-10k, XL: 10-100k, XXL: 100k+ clients connected)
  • Other services hosted on the server
  • Other ports being used on the server
  • Are there other services on separate IPs: Yes/No
  • If yes, which IPs
  • Is legitimate traffic being dropped: YES/NO
  • Was connection to the server lost: YES/NO
  • Which type of legitimate traffic is being dropped

Go further

Enabling and configuring the Edge Network Firewall

Protecting a game server with the application firewall

Join our community of users.

Zugehörige Artikel