AbuseIPDB » 186.122.224.193
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example previewIP Abuse Reports for 186.122.224.193:
This IP address has been reported a total of 19 times from 16 distinct sources. 186.122.224.193 was first reported on , and the most recent report was . In the last 60 days, the top reporter locations were: Germany with 7 reports; United States of America with 4 reports; Austria with 1 report. The most common categories in these recent reports were: Port Scan 10 times; SSH 3 times; Hacking 2 times; Bad Web Bot 2 times; Email Spam 2 times; Other 2 times.
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇩🇪 Jochen Pretli |
connection to honeypot
|
Email Spam Port Scan | ||
| 🇦🇹 urnilxfgbez |
Last 24 Hours suspicious: (DPT=445|DPT=3389|DPT=22|DPT=3306|DPT=8080|DPT=23|DPT=5900|DPT=1433)
|
Port Scan | ||
| Anonymous |
Unauthorized connection to SSH port 22
|
Port Scan SSH | ||
| Anonymous |
suricata IPS/IDS detection, ruleset ET SCAN Potential SSH Scan
|
Port Scan | ||
| Anonymous |
Network service scanning detected by FortiGate; source quarantined.
|
Port Scan | ||
| 🇺🇸 MPL |
tcp/22 (6 or more attempts)
|
Port Scan | ||
| 🇺🇸 RAP |
2026-09-03 06:10:32 UTC Unauthorized activity to TCP port 22. SSH
|
SSH | ||
| 🇩🇪 Jochen Pretli |
connection to honeypot
|
Email Spam Port Scan | ||
| Anonymous |
denied traffic to a honeypot network. destination port 22.
|
Port Scan Hacking | ||
| 🇺🇸 kosada.com |
Web bot: denial-of-service flood
|
DDoS Attack Bad Web Bot | ||
| 🇺🇸 gui-ying233 |
|
Bad Web Bot | ||
| Anonymous |
denied SSH access attempt. destination port 22.
|
Port Scan Brute-Force SSH | ||
| 🇩🇪 EGP Abuse Dept |
Scanning for port/service exploits on tpc-027.mach3builders.nl
|
Port Scan Hacking | ||
| 🇺🇸 TPI-Abuse |
|
Brute-Force Bad Web Bot Web App Attack | ||
| 🇨🇦 polycoda |
🥶 Part of massive botnet scraping campaign that nearly turned into a DDoS on 2025-11-27
|
DDoS Attack |
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩