User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
ACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 2a04:c300:400::9f |
DDoS composite score 16.3 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.235.73.252 |
DDoS composite score 41.8 (proxy tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.66.230.237 |
DDoS composite score 46.7 (proxy tier) - 94 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 171.253.228.145 |
DDoS composite score 29.4 (challenge tier) - 151 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.112.69.18 |
DDoS composite score 29.4 (challenge tier) - 187 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4803:528b:d1d0:f417:d42:7965:818b |
DDoS composite score 36.9 (proxy tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:62d2:e78f:4d70:f3d:63c3:83eb |
DDoS composite score 45.8 (proxy tier) - 70 reqs/5min - waf_repeat_offender
|
DDoS Attack | |
| 🇻🇳 2402:800:6d72:c2a:8148:2504:9100:a5e1 |
DDoS composite score 35.9 (proxy tier) - 145 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.21 |
DDoS composite score 29.4 (challenge tier) - 279 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 136.243.228.182 |
DDoS composite score 25.5 (challenge tier) - 67 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.188.193.133 |
DDoS composite score 25.5 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 205.210.31.198 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.86.63.226 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 58.251.94.154 |
DDoS composite score 19.6 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 66.118.56.46 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 78.142.18.40 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 93.152.221.13 |
DDoS composite score 16.3 (challenge tier) - 11 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:1d9f:5510:b8ae:3d7f:d4a1:92f3 |
DDoS composite score 29.4 (challenge tier) - 69 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 20.195.178.90 |
DDoS composite score 44.8 (proxy tier) - 643 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.243.224 |
DDoS composite score 29.4 (challenge tier) - 267 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 95.211.193.12 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.164.133.138 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.233.213.107 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 2804:14c:de88:9558:840b:e958:bd97:8fb0 |
DDoS composite score 26.1 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 64.89.162.172 |
DDoS composite score 16.3 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack |