User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 66.249.89.170 |
DDoS composite score 43.8 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.72.176.129 |
DDoS composite score 37.9 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 51.103.163.175 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇲🇦 160.179.170.104 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 172.161.16.35 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 195.201.168.79 |
DDoS composite score 37.9 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 2a0b:8bc0:2:7640::1 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.243.230.128 |
DDoS composite score 37.3 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇪🇸 158.158.41.185 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.194.110.188 |
DDoS composite score 60.1 (proxy tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 4.225.163.126 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 123.187.240.242 |
DDoS composite score 37.9 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.89.2 |
DDoS composite score 45.4 (challenge tier) - 59 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 20.203.146.7 |
DDoS composite score 34.6 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 104.28.246.116 |
DDoS composite score 34.6 (challenge tier) - 38 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.68 |
DDoS composite score 57.5 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 54.238.188.92 |
DDoS composite score 48.0 (challenge tier) - 152 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 195.201.111.82 |
DDoS composite score 37.9 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.153.34.151 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.198.83.136 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇹 172.213.241.216 |
DDoS composite score 34.6 (challenge tier) - 60 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.67 |
DDoS composite score 57.5 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇭 20.203.154.158 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 52.231.66.84 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.75 |
DDoS composite score 57.5 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack |