User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 20.120.226.252 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.31.17 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.135.144.126 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.15.51 |
DDoS composite score 19.6 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.155.195.141 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.157.52.37 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇺 46.151.182.58 |
DDoS composite score 16.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.152 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 91.92.42.182 |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 91.92.243.248 |
DDoS composite score 19.6 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 180.242.128.46 |
DDoS composite score 47.7 (proxy tier) - 457 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇱 186.189.72.119 |
DDoS composite score 35.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 198.190.4.249 |
DDoS composite score 25.5 (challenge tier) - 83 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6343:2afe:ad27:932:f0f1:de1e |
DDoS composite score 16.3 (challenge tier) - 29 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:b27a:1e10:7dc7:330:e9ff:c468 |
DDoS composite score 15.0 (challenge tier) - 104 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.242.39 |
DDoS composite score 25.5 (challenge tier) - 67 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 79.127.129.198 |
DDoS composite score 49.0 (proxy tier) - 173 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 117.5.152.110 |
DDoS composite score 22.5 (challenge tier) - 184 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 136.243.228.182 |
DDoS composite score 25.5 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 27.77.245.195 |
DDoS composite score 16.3 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:4c79:f6b0:89f6:875d:3f0f:c19f |
DDoS composite score 25.5 (challenge tier) - 91 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 2401:4900:88a2:3cfe:8811:585d:41b7:7d5c |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.114.56.26 |
DDoS composite score 18.6 (challenge tier) - 125 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.131.23.154 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.135.144.81 |
DDoS composite score 38.9 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack |