Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
i got a lot of those ip’s in my logs, 85.159.237.219, against xmlrpc.php. googling xmlrpc.php seems like its a wordpress security vulnerability, so youve got the dame dude trying to hack/crash your site.
By the way, this is what toplooks like after services restart
I managed to fix the problem. By preventing access to xmlrpc.php in my nginx.conf ( http://bit.ly/1SfjFJ2 ) and setting up fail2ban, everything is working as it should.
Ive set up fail2ban following the DO-tutorial ( http://do.co/1W2mXhQ ) with mail-notifications, and the first 12-hours or so I got about 20 ban-notifications. As soon as it started banning ip-adresses - 30 minutes after configuration - php5-fpm stopped failing.
Thank you @petercollins83 for pointing out the suspicious IP-adress and the xmlrpc.php-issue!