User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 74.7.227.167 |
DDoS composite score 60.1 (proxy tier) - 100 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 38.248.95.254 |
DDoS composite score 33.7 (challenge tier) - 44 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.242.6 |
DDoS composite score 43.8 (challenge tier) - 60 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.107.216.4 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a09:bac5:a6c4:2769::3ed:26 |
DDoS composite score 40.8 (challenge tier) - 104 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.91.2.126 |
DDoS composite score 50.3 (challenge tier) - 241 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 139.99.236.252 |
DDoS composite score 31.7 (challenge tier) - 166 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 20.198.83.136 |
DDoS composite score 34.6 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 113.31.186.146 |
DDoS composite score 37.9 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 35.219.26.61 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 62.171.154.215 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 149.102.234.29 |
DDoS composite score 34.6 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 3.145.75.10 |
DDoS composite score 43.8 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.77.167.26 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇼 35.221.150.166 |
DDoS composite score 37.9 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 164.92.107.174 |
DDoS composite score 34.6 (challenge tier) - 34 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 157.55.39.53 |
DDoS composite score 34.6 (challenge tier) - 5 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 222.253.125.102 |
DDoS composite score 36.9 (challenge tier) - 110 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 100.24.118.139 |
DDoS composite score 36.9 (challenge tier) - 124 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 143.244.168.161 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 147.182.149.75 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 167.172.158.128 |
DDoS composite score 34.6 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 178.128.207.138 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.6.208.74 |
DDoS composite score 34.6 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.196.197.230 |
DDoS composite score 60.1 (proxy tier) - 57 reqs/5min - high_traffic
|
DDoS Attack |