Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United States of America

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbotsspam
Jul 19 05:59:15 vmd26974 sshd[28308]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.195.178.249
Jul 19 05:59:17 vmd26974 sshd[28308]: Failed password for invalid user ki from 34.195.178.249 port 33744 ssh2
...
2020-07-19 12:15:18
attackspam
2020-07-16T13:22:01.763223SusPend.routelink.net.id sshd[57189]: Invalid user ubuntu from 34.195.178.249 port 34910
2020-07-16T13:22:04.216938SusPend.routelink.net.id sshd[57189]: Failed password for invalid user ubuntu from 34.195.178.249 port 34910 ssh2
2020-07-16T13:30:00.795686SusPend.routelink.net.id sshd[58148]: Invalid user 1 from 34.195.178.249 port 37238
...
2020-07-16 18:13:13
attack
Lines containing failures of 34.195.178.249
Jul 13 14:03:11 viking sshd[2922]: Invalid user minecraft from 34.195.178.249 port 49236
Jul 13 14:03:11 viking sshd[2922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.195.178.249 
Jul 13 14:03:13 viking sshd[2922]: Failed password for invalid user minecraft from 34.195.178.249 port 49236 ssh2
Jul 13 14:03:13 viking sshd[2922]: Received disconnect from 34.195.178.249 port 49236:11: Bye Bye [preauth]
Jul 13 14:03:13 viking sshd[2922]: Disconnected from invalid user minecraft 34.195.178.249 port 49236 [preauth]
Jul 13 14:10:57 viking sshd[8965]: Invalid user huy from 34.195.178.249 port 46946
Jul 13 14:10:57 viking sshd[8965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.195.178.249 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=34.195.178.249
2020-07-14 00:49:22
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.195.178.249
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45865
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;34.195.178.249.			IN	A

;; AUTHORITY SECTION:
.			232	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2020071300 1800 900 604800 86400

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jul 14 00:49:14 CST 2020
;; MSG SIZE  rcvd: 118
Host info
249.178.195.34.in-addr.arpa domain name pointer ec2-34-195-178-249.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
249.178.195.34.in-addr.arpa	name = ec2-34-195-178-249.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
91.232.96.26 attack
Jan 30 06:54:35 grey postfix/smtpd\[24961\]: NOQUEUE: reject: RCPT from seventy.msaysha.com\[91.232.96.26\]: 554 5.7.1 Service unavailable\; Client host \[91.232.96.26\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[91.232.96.26\]\; from=\ to=\ proto=ESMTP helo=\
...
2020-01-30 20:46:13
190.64.204.140 attack
Invalid user bjorn from 190.64.204.140 port 34104
2020-01-30 21:13:03
14.190.237.215 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 30-01-2020 04:55:16.
2020-01-30 21:22:11
88.152.231.197 attack
Unauthorized connection attempt detected from IP address 88.152.231.197 to port 2220 [J]
2020-01-30 20:42:26
216.244.66.229 attackbots
Automated report (2020-01-30T12:51:28+00:00). Misbehaving bot detected at this address.
2020-01-30 20:55:14
61.69.198.154 attackbots
Unauthorized connection attempt detected from IP address 61.69.198.154 to port 23 [J]
2020-01-30 21:00:57
75.165.168.77 attackspam
port scan and connect, tcp 23 (telnet)
2020-01-30 20:56:11
51.75.29.61 attack
5x Failed Password
2020-01-30 20:57:27
198.167.138.124 attack
2019-11-19T20:17:07.278Z CLOSE host=198.167.138.124 port=41262 fd=4 time=20.019 bytes=23
...
2020-01-30 20:54:37
218.92.0.199 attackbotsspam
Jan 30 11:10:13 legacy sshd[22527]: Failed password for root from 218.92.0.199 port 21698 ssh2
Jan 30 11:11:07 legacy sshd[22548]: Failed password for root from 218.92.0.199 port 52047 ssh2
...
2020-01-30 20:47:13
61.72.210.201 attackbotsspam
20/1/29@23:55:35: FAIL: IoT-Telnet address from=61.72.210.201
...
2020-01-30 21:05:56
200.16.132.202 attackspambots
Jan 30 14:46:26 pkdns2 sshd\[43741\]: Invalid user cheedella from 200.16.132.202Jan 30 14:46:29 pkdns2 sshd\[43741\]: Failed password for invalid user cheedella from 200.16.132.202 port 39003 ssh2Jan 30 14:49:12 pkdns2 sshd\[43925\]: Invalid user riyaz from 200.16.132.202Jan 30 14:49:14 pkdns2 sshd\[43925\]: Failed password for invalid user riyaz from 200.16.132.202 port 48517 ssh2Jan 30 14:56:03 pkdns2 sshd\[44386\]: Invalid user divena from 200.16.132.202Jan 30 14:56:05 pkdns2 sshd\[44386\]: Failed password for invalid user divena from 200.16.132.202 port 39315 ssh2
...
2020-01-30 21:22:35
37.79.140.101 attackbotsspam
TCP Port Scanning
2020-01-30 21:26:24
182.61.162.54 attack
Unauthorized connection attempt detected from IP address 182.61.162.54 to port 2220 [J]
2020-01-30 21:05:14
51.75.52.127 attackbotsspam
Unauthorized connection attempt detected from IP address 51.75.52.127 to port 8085 [J]
2020-01-30 20:49:08

Recently Reported IPs

115.76.243.100 112.235.172.217 202.195.100.213 192.143.94.47
182.155.219.79 81.128.64.220 131.31.65.65 148.0.76.238
241.235.255.75 227.93.19.137 38.102.4.54 169.159.130.225
57.51.158.0 152.80.165.110 129.28.213.164 118.36.102.70
45.249.40.50 49.206.27.238 190.83.84.210 13.55.52.50