User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
ACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 74.7.241.145 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 200.128.9.8 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.164.192.151 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.138.133.147 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.196.253.189 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee1:df17:4140:7d3f:7e20:43e4:3c07 |
DDoS composite score 16.3 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:62db:4c11:9c04:59a3:507d:de70 |
DDoS composite score 18.6 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.123.170.104 |
DDoS composite score 32.0 (proxy tier) - 81 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:6b32:1eb0:cd0c:929:9de2:47d8 |
DDoS composite score 22.5 (challenge tier) - 173 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:5351:8130:a0cc:a516:f2b0:d2d6 |
DDoS composite score 22.5 (challenge tier) - 176 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 104.196.48.129 |
DDoS composite score 27.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.228.156.129 |
DDoS composite score 22.5 (challenge tier) - 483 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 103.156.2.230 |
DDoS composite score 29.4 (challenge tier) - 296 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.236.164.89 |
DDoS composite score 25.5 (challenge tier) - 86 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6396:8772:1789:a9cb:6db4:982 |
DDoS composite score 18.6 (challenge tier) - 132 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 160.187.68.214 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇪 198.235.24.212 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 162.14.81.106 |
DDoS composite score 26.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.66.151.37 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 95.134.92.184 |
DDoS composite score 16.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 49.51.243.95 |
DDoS composite score 26.1 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 130.89.144.166 |
DDoS composite score 15.4 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.12.191.99 |
DDoS composite score 18.3 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 129.211.229.121 |
DDoS composite score 19.6 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 64.89.162.167 |
DDoS composite score 16.3 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack |