User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇰🇷 43.155.157.239 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.155.188.157 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.157.53.115 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.159.148.221 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.165.174.53 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.166.7.113 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.166.136.24 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.166.224.244 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 49.12.132.45 |
DDoS composite score 16.3 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 49.51.33.159 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇺 64.89.161.160 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 91.148.244.131 |
DDoS composite score 16.3 (challenge tier) - 31 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 141.98.11.134 |
DDoS composite score 20.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 151.246.213.233 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 162.62.231.139 |
DDoS composite score 29.1 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.143.6 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.165.76 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.180.246 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.192.3 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.197.109 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 185.177.72.24 |
DDoS composite score 16.3 (challenge tier) - 47 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 193.148.56.79 |
DDoS composite score 16.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2601:188:c683:a4c0:518:75f7:fc41:32c4 |
DDoS composite score 41.8 (proxy tier) - 91 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 2804:37f0:fc68:e300:7587:583b:965b:6d34 |
DDoS composite score 35.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇺 2a09:bac5:51ae:369::57:21a |
DDoS composite score 35.9 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack |