Port scan from another DO address

I am running a Debian droplet and I have shorewall installed. I block all ports except the ones I need. I use logwatch to keep an eye on my logs for any suspicious activity. I noticed a tcp sync scan to what appears to be every port from 1 to 65535. When I did a whois on the offending ip4 address the net block is assigned to digital ocean. Is this worth creating a trouble ticket for this? I use non-standard ports for services like ssh and of course this scan has revealed these ports to someone. Does DO care that one of their addresses is involved in a port scan like this? This appears to be the only time this address has appeared in my logs for the past month or so.

Thanks for any comments.


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.

The port scan you saw in your logs was a part of a project right here at DO. I’ll do my best to explain a bit more. These scans should have little to no impact on your droplets – They are simple port scans, as we do not wish to set off any alarms or be an inconvenience. If anything, we are trying our best to help provide a better experience for our customers going forward.

Our team set up a few port scans and we’ve been working with this data to see how we can be more proactive about helping our customers avoid having their droplets from being compromised. I apologize if this scan appeared to be malicious in any way. That certainly was not our intent. We’ll be talking internally about how we can be more transparent about this as we move forward. Do you have any suggestions on steps we could take to make this more clear to you? Additionally, please let us know if you would like us to opt you out of this scan, and/or if you would like more information on this project.

There’s nothing dangerous about a scan. You have been scanned already many times.

If you want to report abuse, you should use as indicated in the WHOIS information for the IP address blocks.

By the way, this is why changing the default port of services like SSH is absolutely useless.