Help during an ongoing attack
Under DDoS attack?Take action now.
When services go down, clear information and the right contact matter. Report the incident and have the affected IP addresses, the time it started and a callback number ready.
View the first stepsFirst steps during an attack
Establish the impact
Which services and IP addresses are affected? Check reachability from a second network, bandwidth, packet loss and server load. An outage alone does not confirm a DDoS attack.
Involve your provider
Contact your hosting or network provider through the agreed emergency channel. If a link is saturated, filtering must take place before the bottleneck; local rules alone are not enough.
Preserve observations
Record the start time, time zone, measurements and changes. Coordinate filter or routing changes with your provider and check legitimate traffic afterwards. Keep a working callback channel available.
How filtering works once connected
Our protection learns the regular traffic patterns of your services. Adaptive learning pauses during an attack. Filtering remains active using the baseline previously learned from legitimate traffic.
Understand profiling and filteringTechnical background: RFC 4732 — Internet Denial-of-Service Considerations
For the first conversation
Help us assess the incident.
Fill in what you know and send the details to noc@nuxoa.de. Leave unknown values blank. Do not wait for a complete analysis before contacting us.
The brief stays in this browser tab and is not sent or saved here. Do not enter passwords, credentials or full packet captures.