User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 64.233.172.67 |
DDoS composite score 57.5 (challenge tier) - 58 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.73 |
DDoS composite score 57.5 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.153.182.11 |
DDoS composite score 47.4 (challenge tier) - 200 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 161.97.159.93 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 87.121.84.98 |
DDoS composite score 52.3 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇪🇸 158.158.112.230 |
DDoS composite score 34.6 (challenge tier) - 50 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.154.143.25 |
DDoS composite score 38.6 (challenge tier) - 103 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.74 |
DDoS composite score 57.5 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 222.167.107.41 |
DDoS composite score 34.6 (challenge tier) - 14 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 40.115.139.4 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 107.175.216.43 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 192.144.91.105 |
DDoS composite score 34.6 (challenge tier) - 26 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 162.19.55.99 |
DDoS composite score 43.8 (challenge tier) - 71 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 85.11.167.19 |
DDoS composite score 40.8 (challenge tier) - 103 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 54.198.78.225 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 168.119.80.126 |
DDoS composite score 37.9 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 64.225.69.145 |
DDoS composite score 43.8 (challenge tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 155.94.166.42 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 176.65.132.241 |
DDoS composite score 37.3 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.151.174 |
DDoS composite score 43.8 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 146.190.17.124 |
DDoS composite score 36.9 (challenge tier) - 129 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 20.166.31.184 |
DDoS composite score 36.9 (challenge tier) - 111 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 54.238.188.92 |
DDoS composite score 64.1 (proxy tier) - 153 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 61 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 20.215.69.226 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack |