User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇦🇺 20.211.123.94 |
DDoS composite score 34.6 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇪🇸 158.158.41.185 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 20.100.169.43 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 68.233.37.50 |
DDoS composite score 37.9 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 155.94.168.26 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇳🇱 2a0b:8bc0:2:b562::1 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 31.121.111.20 |
DDoS composite score 36.9 (challenge tier) - 139 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.196.201.163 |
DDoS composite score 34.6 (challenge tier) - 48 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.78.145.252 |
DDoS composite score 34.6 (challenge tier) - 48 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 98.83.221.39 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 45.147.70.73 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 72.63.129.128 |
DDoS composite score 34.6 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 172.161.16.35 |
DDoS composite score 37.3 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.77 |
DDoS composite score 57.5 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 172.94.9.253 |
DDoS composite score 46.1 (challenge tier) - 59 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 20.91.253.196 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.63.209.197 |
DDoS composite score 34.6 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2600:1900:4090:1d:0:2ce:: |
DDoS composite score 47.7 (challenge tier) - 164 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 20.203.186.201 |
DDoS composite score 37.3 (challenge tier) - 68 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 51.107.222.225 |
DDoS composite score 57.2 (challenge tier) - 152 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 91.224.92.35 |
DDoS composite score 42.5 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 128.242.233.28 |
DDoS composite score 34.6 (challenge tier) - 48 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇪🇸 68.221.128.94 |
DDoS composite score 36.9 (challenge tier) - 107 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2607:f8b0:4001:c47::e |
DDoS composite score 43.8 (challenge tier) - 82 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 185.177.72.17 |
DDoS composite score 68.0 (proxy tier) - 527 reqs/5min - high_traffic
|
DDoS Attack |