User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇬🇧 149.248.78.164 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 159.89.127.165 |
DDoS composite score 21.2 (challenge tier) - 20 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2607:f8b0:400c:c29::a |
DDoS composite score 32.0 (proxy tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6343:332d:d58:35d7:a6da:9e72 |
DDoS composite score 29.4 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.182.175.92 |
DDoS composite score 22.5 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 45.45.237.192 |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇪🇸 45.92.84.242 |
DDoS composite score 24.2 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 78.142.18.172 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 104.28.243.189 |
DDoS composite score 39.9 (proxy tier) - 105 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 147.185.132.82 |
DDoS composite score 38.9 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 155.94.203.197 |
DDoS composite score 21.2 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 180.149.4.81 |
DDoS composite score 21.2 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:61d:3280:b92a:5063:e3d1:6fd0 |
DDoS composite score 25.5 (challenge tier) - 141 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇺 91.197.160.165 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:53f8:af10:a957:5f2f:58c1:c047 |
DDoS composite score 25.5 (challenge tier) - 109 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 119.249.100.171 |
DDoS composite score 16.3 (challenge tier) - 2 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.162.179.214 |
DDoS composite score 22.5 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.115.42.117 |
DDoS composite score 25.5 (challenge tier) - 84 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 49.51.204.74 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 58.187.156.93 |
DDoS composite score 25.5 (challenge tier) - 78 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 116.47.170.156 |
DDoS composite score 32.0 (proxy tier) - 80 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 157.143.3.35 |
DDoS composite score 19.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 185.191.171.3 |
DDoS composite score 19.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6131:8c07:a5f1:8c88:659b:eb0a |
DDoS composite score 18.6 (challenge tier) - 102 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 125.235.234.182 |
DDoS composite score 25.5 (challenge tier) - 129 reqs/5min - high_traffic
|
DDoS Attack |