AbuseIPDB » 139.59.20.111

139.59.20.111 was found in our database!

This IP was reported 355 times. Confidence of Abuse is 0%: ?

0%

ISP	Digital Ocean Inc.
Usage Type	Data Center/Web Hosting/Transit
Domain Name	digitalocean.com
Country	India
City	Bangalore, Karnataka

Spot an error? IP info including ISP, Usage Type, and Location provided by IP2Location.

Report 139.59.20.111

Whois 139.59.20.111

IP Abuse Reports for 139.59.20.111:

This IP address has been reported a total of 355 times from 77 distinct sources. 139.59.20.111 was first reported on September 27th 2018, and the most recent report was 4 months ago.

Old Reports: The most recent abuse report for this IP address is from 4 months ago. It is possible that this IP is no longer involved in abusive activities.

Reporter	Date	Comment	Categories
herz-der-gamer.de	02 Feb 2019	Nov 30 20:13:47 marvibiene sshd[25665]: Invalid user summer from 139.59.20.111 port 56216 Nov ... show moreNov 30 20:13:47 marvibiene sshd[25665]: Invalid user summer from 139.59.20.111 port 56216 Nov 30 20:13:47 marvibiene sshd[25665]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 ... show less	Brute-Force
mfb	03 Jan 2019		Brute-Force SSH
AbuseIPDB	02 Jan 2019	Triggered by Fail2Ban at Vostok web server	Brute-Force SSH
dreamzgc.com	01 Jan 2019	Jan 1 16:13:59 dedicated sshd\[12501\]: Invalid user sinusbot from 139.59.20.111 port 37566 J ... show moreJan 1 16:13:59 dedicated sshd\[12501\]: Invalid user sinusbot from 139.59.20.111 port 37566 Jan 1 16:13:59 dedicated sshd\[12501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Jan 1 16:14:01 dedicated sshd\[12501\]: Failed password for invalid user sinusbot from 139.59.20.111 port 37566 ssh2 show less	Brute-Force SSH
Mako Scientific	01 Jan 2019	ms-sf1-01 recorded 3 login violations from 139.59.20.111 and was blocked at 2019-01-01 13:52:08. 139 ... show morems-sf1-01 recorded 3 login violations from 139.59.20.111 and was blocked at 2019-01-01 13:52:08. 139.59.20.111 has been blocked on 8 previous occasions. 139.59.20.111's first attempt was recorded at 2018-09-28 20:23:20 show less	Brute-Force SSH
ncomp.co.za	01 Jan 2019	Jan 1 10:05:29 ncomp sshd[6484]: Invalid user informix from 139.59.20.111 Jan 1 10:05:29 nco ... show moreJan 1 10:05:29 ncomp sshd[6484]: Invalid user informix from 139.59.20.111 Jan 1 10:05:29 ncomp sshd[6484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Jan 1 10:05:29 ncomp sshd[6484]: Invalid user informix from 139.59.20.111 Jan 1 10:05:31 ncomp sshd[6484]: Failed password for invalid user informix from 139.59.20.111 port 39496 ssh2 ... show less	Brute-Force SSH
C A T	31 Dec 2018	Jan 1 02:01:45 h2177944 sshd\[29851\]: Invalid user postgres from 139.59.20.111 port 37012 Ja ... show moreJan 1 02:01:45 h2177944 sshd\[29851\]: Invalid user postgres from 139.59.20.111 port 37012 Jan 1 02:01:45 h2177944 sshd\[29851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Jan 1 02:01:48 h2177944 sshd\[29851\]: Failed password for invalid user postgres from 139.59.20.111 port 37012 ssh2 Jan 1 02:29:29 h2177944 sshd\[30328\]: Invalid user samba from 139.59.20.111 port 49364 ... show less	Hacking
Anonymous	30 Dec 2018	Dec 30 15:09:56 bouncer sshd\[26780\]: Invalid user teamspeak from 139.59.20.111 port 57868 De ... show moreDec 30 15:09:56 bouncer sshd\[26780\]: Invalid user teamspeak from 139.59.20.111 port 57868 Dec 30 15:09:56 bouncer sshd\[26780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Dec 30 15:09:58 bouncer sshd\[26780\]: Failed password for invalid user teamspeak from 139.59.20.111 port 57868 ssh2 ... show less	Brute-Force SSH
Anonymous	30 Dec 2018	Dec 30 13:44:18 bouncer sshd\[25949\]: Invalid user pppp from 139.59.20.111 port 49154 Dec 30 ... show moreDec 30 13:44:18 bouncer sshd\[25949\]: Invalid user pppp from 139.59.20.111 port 49154 Dec 30 13:44:18 bouncer sshd\[25949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Dec 30 13:44:20 bouncer sshd\[25949\]: Failed password for invalid user pppp from 139.59.20.111 port 49154 ssh2 ... show less	Brute-Force SSH
florian-emperhoff.de	29 Dec 2018	Dec 30 03:17:11 sv1 sshd\[3669\]: Invalid user ge from 139.59.20.111 port 51210 Dec 30 03:17:1 ... show moreDec 30 03:17:11 sv1 sshd\[3669\]: Invalid user ge from 139.59.20.111 port 51210 Dec 30 03:17:11 sv1 sshd\[3669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Dec 30 03:17:13 sv1 sshd\[3669\]: Failed password for invalid user ge from 139.59.20.111 port 51210 ssh2 ... show less	Brute-Force SSH
Sumeragi	29 Dec 2018		SSH
florian-emperhoff.de	29 Dec 2018	Dec 30 01:54:52 sv1 sshd\[779\]: Invalid user ec2-user from 139.59.20.111 port 42668 Dec 30 01 ... show moreDec 30 01:54:52 sv1 sshd\[779\]: Invalid user ec2-user from 139.59.20.111 port 42668 Dec 30 01:54:52 sv1 sshd\[779\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Dec 30 01:54:53 sv1 sshd\[779\]: Failed password for invalid user ec2-user from 139.59.20.111 port 42668 ssh2 ... show less	Brute-Force SSH
AmiT177	29 Dec 2018		Brute-Force SSH
Anonymous	29 Dec 2018	Dec 29 13:28:51 srv206 sshd[23309]: Invalid user www from 139.59.20.111 ...	Brute-Force SSH
Anonymous	29 Dec 2018	Dec 29 11:36:56 srv206 sshd[23023]: Invalid user support from 139.59.20.111 Dec 29 11:36:56 sr ... show moreDec 29 11:36:56 srv206 sshd[23023]: Invalid user support from 139.59.20.111 Dec 29 11:36:56 srv206 sshd[23023]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.20.111 Dec 29 11:36:56 srv206 sshd[23023]: Invalid user support from 139.59.20.111 Dec 29 11:36:57 srv206 sshd[23023]: Failed password for invalid user support from 139.59.20.111 port 55102 ssh2 ... show less	Brute-Force SSH

Is this your IP? You may request to takedown any associated reports. We will attempt to verify your ownership. Request Takedown 🚩