User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇱🇹 91.224.92.99 |
DDoS composite score 65.0 (proxy tier) - 384 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 51.103.163.175 |
DDoS composite score 37.3 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.242.0 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 85.11.167.155 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.89.128.74 |
DDoS composite score 37.3 (challenge tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.72.176.129 |
DDoS composite score 37.9 (challenge tier) - 43 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.73 |
DDoS composite score 54.9 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 74.248.157.73 |
DDoS composite score 40.8 (challenge tier) - 207 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 20.215.65.4 |
DDoS composite score 37.3 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.48.184.58 |
DDoS composite score 34.6 (challenge tier) - 46 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 152.32.234.39 |
DDoS composite score 34.6 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 104.164.44.220 |
DDoS composite score 34.6 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.117.11.68 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 176.65.132.241 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 54.238.188.92 |
DDoS composite score 48.0 (challenge tier) - 192 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.173.47.165 |
DDoS composite score 43.8 (challenge tier) - 74 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.67 |
DDoS composite score 54.9 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.77.167.17 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 20.199.113.127 |
DDoS composite score 32.4 (challenge tier) - 95 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇹 172.213.0.122 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 74.248.37.20 |
DDoS composite score 34.6 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 51.107.217.61 |
DDoS composite score 34.6 (challenge tier) - 46 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 72 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 4.225.164.196 |
DDoS composite score 37.3 (challenge tier) - 64 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 216.73.216.155 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack |