Server down because of portflood attack by the server

Hi Guys,

Kindly help me on these,

I received below messages from the server people,

"your Server/Customer with the IP: x.x.x.x (x.x.x.x) has attacked one of our servers/partners. The attackers used the method/service: portflood on: Thu, 04 Aug 2016 13:59:17 +0200. The time listed is from the server-time of the Blocklist-user who submitted the report. The attack was reported to the on: Thu, 04 Aug 2016 13:59:37 +0200

The IP has been automatically blocked for a period of time. For an IP to be blocked, it needs to have made several failed logins (ssh, imap…), tried to log in for an “invalid user”, or have triggered several 5xx-Error-Codes (eg. Blacklist on email…), all during a short period of time. The Server-Owner configures the number of failed attempts, and the time period they have to occur in, in order to trigger a ban and report. Blocklist has no control over these settings.

Please check the machine behind the IP x.x.x.x (x.x.x.x) and fix the problem. To search for AS-Number/IPs that you control, to see if any others have been infected/blocked, please go to:"


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Based on this information, chances are that your server is compromised. Without any further information the only course of action I can recommend is to take the server offline and investigate. You will most likely want to re-deploy from a clean backup.

This guide should help you with the next steps.