User hirosume2 joined AbuseIPDB in February 2026 and has reported 14,929 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 2600:4040:b5eb:6300:816c:1ad5:3ae7:c791 |
DDoS composite score 40.8 (challenge tier) - 161 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 5.9.50.77 |
DDoS composite score 43.8 (challenge tier) - 59 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.4.250.95 |
DDoS composite score 43.8 (challenge tier) - 99 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 178.156.249.178 |
DDoS composite score 37.9 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 69.164.96.99 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇦🇺 20.211.123.94 |
DDoS composite score 34.6 (challenge tier) - 48 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 90 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.89.170 |
DDoS composite score 41.2 (challenge tier) - 51 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 185.152.37.56 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.77.66 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 206.189.225.181 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 139.59.132.8 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.23.218.208 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 159.89.174.87 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 136.226.236.125 |
DDoS composite score 38.6 (challenge tier) - 114 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4800:1f0b:1d00:d847:566:8ad4:97bb |
DDoS composite score 40.8 (challenge tier) - 288 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.120 |
DDoS composite score 40.5 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.204.179.249 |
DDoS composite score 36.9 (challenge tier) - 107 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.217.131 |
DDoS composite score 43.8 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 54.89.198.203 |
DDoS composite score 51.6 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.125.151.174 |
DDoS composite score 43.8 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.167.144.204 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 178.104.124.96 |
DDoS composite score 37.9 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.198.83.136 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.200.222.0 |
DDoS composite score 43.8 (challenge tier) - 75 reqs/5min - high_traffic
|
DDoS Attack |