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

Region: Oregon

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#


NetRange:       52.0.0.0 - 52.79.255.255
CIDR:           52.64.0.0/12, 52.0.0.0/10
NetName:        AT-88-Z
NetHandle:      NET-52-0-0-0-1
Parent:         NET52 (NET-52-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Amazon Technologies Inc. (AT-88-Z)
RegDate:        1991-12-19
Updated:        2024-02-05
Comment:        Geofeed http://ip-ranges.amazonaws.com/geo-ip-feed.csv
Ref:            https://rdap.arin.net/registry/ip/52.0.0.0



OrgName:        Amazon Technologies Inc.
OrgId:          AT-88-Z
Address:        410 Terry Ave N.
City:           Seattle
StateProv:      WA
PostalCode:     98109
Country:        US
RegDate:        2011-12-08
Updated:        2024-01-24
Comment:        All abuse reports MUST include:
Comment:        * src IP
Comment:        * dest IP (your IP)
Comment:        * dest port
Comment:        * Accurate date/timestamp and timezone of activity
Comment:        * Intensity/frequency (short log extracts)
Comment:        * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref:            https://rdap.arin.net/registry/entity/AT-88-Z


OrgNOCHandle: AANO1-ARIN
OrgNOCName:   Amazon AWS Network Operations
OrgNOCPhone:  +1-206-555-0000 
OrgNOCEmail:  amzn-noc-contact@amazon.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/AANO1-ARIN

OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName:   IP Routing
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/IPROU3-ARIN

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName:   Amazon EC2 Abuse
OrgAbusePhone:  +1-206-555-0000 
OrgAbuseEmail:  trustandsafety@support.aws.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName:   Amazon EC2 Network Operations
OrgTechPhone:  +1-206-555-0000 
OrgTechEmail:  amzn-noc-contact@amazon.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ANO24-ARIN

OrgRoutingHandle: ARMP-ARIN
OrgRoutingName:   AWS RPKI Management POC
OrgRoutingPhone:  +1-206-555-0000 
OrgRoutingEmail:  aws-rpki-routing-poc@amazon.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/ARMP-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.27.246.218
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2201
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.27.246.218.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Nov 11 12:00:09 CST 2025
;; MSG SIZE  rcvd: 106
Host info
218.246.27.52.in-addr.arpa domain name pointer ec2-52-27-246-218.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
218.246.27.52.in-addr.arpa	name = ec2-52-27-246-218.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.90.118.18 attack
10/14/2019-00:46:25.013659 185.90.118.18 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 12:56:42
117.159.84.145 attack
Automatic report - Banned IP Access
2019-10-14 12:36:13
153.36.242.143 attackbotsspam
Oct 14 00:14:23 plusreed sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.36.242.143  user=root
Oct 14 00:14:25 plusreed sshd[31623]: Failed password for root from 153.36.242.143 port 13626 ssh2
...
2019-10-14 12:16:07
222.186.30.152 attack
Oct 14 06:51:38 andromeda sshd\[13691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.152  user=root
Oct 14 06:51:40 andromeda sshd\[13691\]: Failed password for root from 222.186.30.152 port 30128 ssh2
Oct 14 06:51:42 andromeda sshd\[13691\]: Failed password for root from 222.186.30.152 port 30128 ssh2
2019-10-14 12:52:41
186.215.234.110 attack
Oct 13 18:14:22 web9 sshd\[4517\]: Invalid user Seven123 from 186.215.234.110
Oct 13 18:14:22 web9 sshd\[4517\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.215.234.110
Oct 13 18:14:23 web9 sshd\[4517\]: Failed password for invalid user Seven123 from 186.215.234.110 port 54639 ssh2
Oct 13 18:22:33 web9 sshd\[5655\]: Invalid user Restaurant@2017 from 186.215.234.110
Oct 13 18:22:33 web9 sshd\[5655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.215.234.110
2019-10-14 12:25:26
119.10.115.36 attack
Oct 13 17:51:52 auw2 sshd\[23835\]: Invalid user Qwerty\#111 from 119.10.115.36
Oct 13 17:51:52 auw2 sshd\[23835\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.10.115.36
Oct 13 17:51:53 auw2 sshd\[23835\]: Failed password for invalid user Qwerty\#111 from 119.10.115.36 port 42098 ssh2
Oct 13 17:58:05 auw2 sshd\[24332\]: Invalid user Coeur2017 from 119.10.115.36
Oct 13 17:58:05 auw2 sshd\[24332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.10.115.36
2019-10-14 12:30:15
222.186.180.223 attackbotsspam
Oct 12 08:11:46 microserver sshd[33125]: Failed none for root from 222.186.180.223 port 56410 ssh2
Oct 12 08:11:47 microserver sshd[33125]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Oct 12 08:11:49 microserver sshd[33125]: Failed password for root from 222.186.180.223 port 56410 ssh2
Oct 12 08:11:54 microserver sshd[33125]: Failed password for root from 222.186.180.223 port 56410 ssh2
Oct 12 08:11:58 microserver sshd[33125]: Failed password for root from 222.186.180.223 port 56410 ssh2
Oct 12 11:13:01 microserver sshd[58133]: Failed none for root from 222.186.180.223 port 21920 ssh2
Oct 12 11:13:02 microserver sshd[58133]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Oct 12 11:13:04 microserver sshd[58133]: Failed password for root from 222.186.180.223 port 21920 ssh2
Oct 12 11:13:09 microserver sshd[58133]: Failed password for root from 222.186.180.223 port 21920 ssh2
2019-10-14 12:44:48
185.90.118.84 attackspam
10/14/2019-00:26:42.006438 185.90.118.84 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 12:48:24
178.46.167.194 attackbotsspam
Automatic report - Banned IP Access
2019-10-14 12:42:29
173.239.37.152 attack
2019-10-14T04:46:43.115968shield sshd\[7419\]: Invalid user Jelszo1! from 173.239.37.152 port 44260
2019-10-14T04:46:43.123507shield sshd\[7419\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.239.37.152
2019-10-14T04:46:45.439031shield sshd\[7419\]: Failed password for invalid user Jelszo1! from 173.239.37.152 port 44260 ssh2
2019-10-14T04:50:11.283764shield sshd\[8755\]: Invalid user Amigo1@3 from 173.239.37.152 port 53368
2019-10-14T04:50:11.287812shield sshd\[8755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.239.37.152
2019-10-14 12:55:57
159.89.169.109 attackspambots
2019-10-14T03:58:34.106205abusebot.cloudsearch.cf sshd\[30330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.169.109  user=root
2019-10-14 12:15:41
110.185.106.47 attackbotsspam
Oct 13 17:47:31 php1 sshd\[31065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.185.106.47  user=root
Oct 13 17:47:33 php1 sshd\[31065\]: Failed password for root from 110.185.106.47 port 41994 ssh2
Oct 13 17:52:31 php1 sshd\[31623\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.185.106.47  user=root
Oct 13 17:52:33 php1 sshd\[31623\]: Failed password for root from 110.185.106.47 port 51620 ssh2
Oct 13 17:57:31 php1 sshd\[32187\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.185.106.47  user=root
2019-10-14 12:47:33
154.70.208.66 attack
Oct 14 06:53:13 www sshd\[136357\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.70.208.66  user=root
Oct 14 06:53:15 www sshd\[136357\]: Failed password for root from 154.70.208.66 port 42128 ssh2
Oct 14 06:58:21 www sshd\[136406\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.70.208.66  user=root
...
2019-10-14 12:21:47
222.186.175.150 attackbots
Oct 14 06:06:10 MK-Soft-VM7 sshd[5796]: Failed password for root from 222.186.175.150 port 17578 ssh2
Oct 14 06:06:15 MK-Soft-VM7 sshd[5796]: Failed password for root from 222.186.175.150 port 17578 ssh2
...
2019-10-14 12:15:27
222.186.169.192 attackbots
SSH Brute Force, server-1 sshd[6261]: Failed password for root from 222.186.169.192 port 12176 ssh2
2019-10-14 12:56:27

Recently Reported IPs

119.28.76.230 100.27.10.200 91.231.89.86 91.196.152.100
149.40.55.20 149.40.56.20 124.23.133.16 147.185.132.174
219.136.104.163 82.146.183.213 147.185.132.223 45.135.232.237
95.111.248.83 118.24.50.211 103.149.244.6 2409:8a04:a823:0:fe84:17ff:feec:bd37
2408:841d:8af4:1d58:ec3b:61ff:febf:8010 111.226.204.49 36.99.136.148 192.168.244.34