User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 107.172.195.99 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.242.116.146 |
DDoS composite score 34.6 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.241.29.141 |
DDoS composite score 36.9 (challenge tier) - 139 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.64.163 |
DDoS composite score 36.9 (challenge tier) - 103 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 91.217.249.221 |
DDoS composite score 36.9 (challenge tier) - 127 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 213.209.159.254 |
DDoS composite score 54.2 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.64.162 |
DDoS composite score 36.9 (challenge tier) - 119 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.109.143.198 |
DDoS composite score 47.7 (challenge tier) - 180 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 194.206.77.58 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 51.75.162.18 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.68 |
DDoS composite score 54.9 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 2001:448a:1082:aa41:156a:580:fe5d:3e17 |
DDoS composite score 43.8 (challenge tier) - 141 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.89.226.144 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.109.88.216 |
DDoS composite score 47.7 (challenge tier) - 323 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 168.144.40.70 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.117.70.77 |
DDoS composite score 51.6 (challenge tier) - 953 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.73 |
DDoS composite score 57.5 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇬 45.88.138.44 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.151.209.7 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 119.252.220.118 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.15.7 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 58 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.196.9.39 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 54.37.10.247 |
DDoS composite score 43.8 (challenge tier) - 96 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.74 |
DDoS composite score 54.9 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack |