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: Japan

Internet Service Provider: Amazon Data Services Japan

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbots
2019-09-30T03:47:55.099192hub.schaetter.us sshd\[32383\]: Invalid user user from 13.113.48.208 port 47852
2019-09-30T03:47:55.107008hub.schaetter.us sshd\[32383\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-13-113-48-208.ap-northeast-1.compute.amazonaws.com
2019-09-30T03:47:57.106650hub.schaetter.us sshd\[32383\]: Failed password for invalid user user from 13.113.48.208 port 47852 ssh2
2019-09-30T03:54:55.818361hub.schaetter.us sshd\[32450\]: Invalid user admin from 13.113.48.208 port 35352
2019-09-30T03:54:55.829263hub.schaetter.us sshd\[32450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-13-113-48-208.ap-northeast-1.compute.amazonaws.com
...
2019-09-30 16:13:48
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.113.48.208
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51432
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 102 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 30 16:13:44 CST 2019
;; MSG SIZE  rcvd: 117
Host info
208.48.113.13.in-addr.arpa domain name pointer ec2-13-113-48-208.ap-northeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
208.48.113.13.in-addr.arpa	name = ec2-13-113-48-208.ap-northeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
144.217.255.89 attack
port scan and connect, tcp 22 (ssh)
2020-02-01 23:59:38
148.70.1.210 attackbots
...
2020-02-01 23:57:04
49.88.112.55 attack
$f2bV_matches
2020-02-01 23:48:01
2.237.225.16 attackspambots
Honeypot attack, port: 81, PTR: PTR record not found
2020-02-02 00:14:10
148.235.57.179 attack
Dec 19 20:39:55 v22018076590370373 sshd[842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.57.179 
...
2020-02-02 00:10:27
148.70.121.210 attackbotsspam
Feb  1 12:00:49 firewall sshd[19326]: Invalid user 123qwe from 148.70.121.210
Feb  1 12:00:51 firewall sshd[19326]: Failed password for invalid user 123qwe from 148.70.121.210 port 39528 ssh2
Feb  1 12:05:23 firewall sshd[19552]: Invalid user mcserv from 148.70.121.210
...
2020-02-01 23:49:01
80.211.57.189 attackbots
Feb  1 14:49:14 silence02 sshd[6590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.57.189
Feb  1 14:49:17 silence02 sshd[6590]: Failed password for invalid user minecraft from 80.211.57.189 port 32980 ssh2
Feb  1 14:52:29 silence02 sshd[6750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.57.189
2020-02-01 23:47:19
148.70.178.70 attackspambots
Jan 21 22:10:40 v22018076590370373 sshd[27635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.178.70 
...
2020-02-01 23:35:43
148.66.135.178 attackspambots
Dec  1 16:50:58 v22018076590370373 sshd[11154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.66.135.178 
...
2020-02-01 23:59:04
148.70.11.143 attackspam
...
2020-02-01 23:52:59
148.70.192.84 attackspambots
...
2020-02-01 23:29:10
148.70.134.52 attackbots
Unauthorized connection attempt detected from IP address 148.70.134.52 to port 2220 [J]
2020-02-01 23:45:21
89.248.162.247 attackspambots
883/tcp 294/tcp 971/tcp...
[2019-12-24/2020-02-01]215pkt,215pt.(tcp)
2020-02-01 23:55:57
148.70.128.197 attackbotsspam
...
2020-02-01 23:46:22
148.70.116.223 attackbots
...
2020-02-01 23:49:22

Recently Reported IPs

103.99.38.39 199.116.118.246 114.2.179.57 186.183.150.21
189.102.13.109 119.42.84.92 129.60.30.223 214.129.119.185
172.104.106.221 222.188.21.32 151.41.101.72 107.20.102.243
123.24.205.219 27.64.12.84 118.169.64.114 59.40.83.165
40.73.101.100 123.24.159.161 111.246.114.241 171.224.20.180