User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇮🇳 160.187.68.214 |
DDoS composite score 16.3 (challenge 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 | |
| 🇧🇪 198.235.24.212 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.90.206.63 |
DDoS composite score 18.3 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.169.40.61 |
DDoS composite score 41.8 (proxy tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.19.47.155 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.26.43.210 |
DDoS composite score 22.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 49.51.132.100 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 82.23.90.10 |
DDoS composite score 21.2 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇿 203.94.33.121 |
DDoS composite score 35.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 203.159.90.218 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 216.73.216.23 |
DDoS composite score 25.5 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:620e:9cf4:cd79:d0ff:f750:dbbd |
DDoS composite score 25.5 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 113.160.240.195 |
DDoS composite score 27.1 (challenge tier) - 68 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.235.24.39 |
DDoS composite score 19.6 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.63.87.152 |
DDoS composite score 41.8 (proxy tier) - 72 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 23.27.145.43 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.85.154.114 |
DDoS composite score 38.9 (proxy tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.227.168.71 |
DDoS composite score 49.7 (proxy tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.133.14.237 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 62.60.130.233 |
DDoS composite score 16.3 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 100.58.114.161 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.66.76.25 |
DDoS composite score 22.5 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 194.206.77.58 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2601:207:380:8d60:d8a9:f6a:ee98:cfc3 |
DDoS composite score 19.6 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack |