Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 159.89.29.254:
This IP address has been reported a total of
33
times from
22 distinct
sources.
159.89.29.254 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 17
reports;
Germany
with 5
reports;
United Kingdom of Great Britain and Northern Ireland
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
28
times;
Brute-Force
15
times;
Bad Web Bot
12
times;
Hacking
6
times;
DDoS Attack
4
times;
Other
7
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
3 incidents: web scanning/attack, HTTP flood/DDoS. First: 2026-09-03 13:45, Last: 2026-09-04 06:51 U ...
show more3 incidents: web scanning/attack, HTTP flood/DDoS. First: 2026-09-03 13:45, Last: 2026-09-04 06:51 UTC. Triggers: nginx-sensitive-files,nginx-limit-req,unknown.
show less
CrowdSec detected Known vulnerability exploitation attempt. Scenario: crowdsecurity/CVE-2017-9841. A ...
show moreCrowdSec detected Known vulnerability exploitation attempt. Scenario: crowdsecurity/CVE-2017-9841. Automatic ban triggered. Detection time (UTC): 2026-09-03T22:29:10.589162266Z. Context: http_status=302
show less
Malicious activity in general-malicious. Evidence: (apache_probe) Failed Access (403/404) 159.89.29. ...
show moreMalicious activity in general-malicious. Evidence: (apache_probe) Failed Access (403/404) 159.89.29.254 (DE/Germany/-): 20 in the last 3600 secs | UA: (apache_probe) Failed Access (403/404) 159.89.29.254 (DE/Germany/-): 20 in the last 3600 secs
show less
CrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban tri ...
show moreCrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban triggered. Detection time (UTC): 2026-09-03T21:26:12.92296441Z. Context: http_status=404
show less
3 incidents: web scanning/attack, HTTP flood/DDoS. First: 2026-09-03 13:45, Last: 2026-09-03 13:46 U ...
show more3 incidents: web scanning/attack, HTTP flood/DDoS. First: 2026-09-03 13:45, Last: 2026-09-03 13:46 UTC. Triggers: nginx-noscript,nginx-sensitive-files,nginx-limit-req.
show less
