User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇪🇸 45.92.87.180 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 50.18.34.246 |
DDoS composite score 16.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 54.85.43.101 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 58.187.212.180 |
DDoS composite score 25.5 (challenge tier) - 125 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 138.246.253.24 |
DDoS composite score 38.9 (proxy tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 146.70.194.244 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 147.185.132.99 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 162.62.213.187 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 162.220.13.17 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.35.137 |
DDoS composite score 22.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.37.134 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 193.148.56.148 |
DDoS composite score 16.3 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 202.51.202.242 |
DDoS composite score 19.3 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 213.171.208.62 |
DDoS composite score 19.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 116.110.219.242 |
DDoS composite score 24.2 (challenge tier) - 208 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 213.209.159.254 |
DDoS composite score 19.3 (challenge tier) - 48 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.143 |
DDoS composite score 41.8 (proxy tier) - 97 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 172.241.167.194 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:61ab:b95d:c4f1:44c4:c7e0:ef7f |
DDoS composite score 18.6 (challenge tier) - 111 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 216.73.216.204 |
DDoS composite score 25.5 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:61ae:2342:c19e:387d:710c:5698 |
DDoS composite score 25.5 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:801b:6df0:d191:7702:8e32:bbdc |
DDoS composite score 25.5 (challenge tier) - 72 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.21 |
DDoS composite score 29.4 (challenge tier) - 177 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6d72:c2a:8148:2504:9100:a5e1 |
DDoS composite score 29.4 (challenge tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:4947:a60:c2c6:2890:e318:9faf |
DDoS composite score 35.9 (proxy tier) - 81 reqs/5min - high_traffic
|
DDoS Attack |