User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇻🇳 1.52.9.254 |
DDoS composite score 25.5 (challenge tier) - 60 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 1.53.168.185 |
DDoS composite score 25.5 (challenge tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.62 |
DDoS composite score 19.0 (challenge tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.64 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇲🇻 124.195.206.229 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 147.182.200.94 |
DDoS composite score 16.3 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 216.38.28.47 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 2a09:bac1:36a0:1468::29e:dc |
DDoS composite score 18.3 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:c05e:45c0:98f7:2615:674c:75e2 |
DDoS composite score 29.4 (challenge tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.188.253.211 |
DDoS composite score 25.5 (challenge tier) - 90 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 143.110.213.72 |
DDoS composite score 16.3 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.133.91.48 |
DDoS composite score 19.6 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 73.122.245.244 |
DDoS composite score 16.3 (challenge tier) - 28 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 82.39.212.242 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 109.199.117.174 |
DDoS composite score 16.3 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 134.209.25.199 |
DDoS composite score 16.3 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.250.252.242 |
DDoS composite score 16.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 177.17.242.228 |
DDoS composite score 35.9 (proxy tier) - 26 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 185.156.73.218 |
DDoS composite score 35.9 (proxy tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a09:bac1:76a0:460::5e:4a |
DDoS composite score 16.3 (challenge tier) - 26 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 115.74.255.140 |
DDoS composite score 29.4 (challenge tier) - 154 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:5133:3840:806d:47bc:94:3db8 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2401:d800:a53:d016:211e:1b84:3508:4ab3 |
DDoS composite score 29.4 (challenge tier) - 316 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇶🇦 37.186.41.197 |
DDoS composite score 35.9 (proxy tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇼 198.235.24.101 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack |