User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 85.89.218.14 |
DDoS composite score 34.6 (challenge tier) - 43 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇺🇸 207.46.13.64 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.78.181.132 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 183.134.59.133 |
DDoS composite score 37.9 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.77 |
DDoS composite score 57.5 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 2001:41d0:701:1100::2444 |
DDoS composite score 43.8 (challenge tier) - 66 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 52.187.249.150 |
DDoS composite score 34.6 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 134.209.42.24 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 113.31.186.146 |
DDoS composite score 44.4 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 104.164.173.249 |
DDoS composite score 34.6 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:d847:566:8ad4:97bb |
DDoS composite score 31.4 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.196.201.163 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2600:1900:4120:ceed:0:5e:: |
DDoS composite score 50.3 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇿 195.123.246.15 |
DDoS composite score 34.6 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 62.60.130.224 |
DDoS composite score 59.8 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 52.169.206.229 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 193.32.249.134 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.89.172 |
DDoS composite score 41.2 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇪🇬 197.32.202.27 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:bc41:1a53:50a9:c812 |
DDoS composite score 40.8 (challenge tier) - 222 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 98.93.166.95 |
DDoS composite score 43.8 (challenge tier) - 64 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇪 5.62.21.140 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 93.123.109.214 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 106.75.32.110 |
DDoS composite score 34.6 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 54.238.188.92 |
DDoS composite score 64.1 (proxy tier) - 167 reqs/5min - high_traffic
|
DDoS Attack |