User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
ACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇻🇳 2401:d800:93f:dd1a:2dd4:d09:7b29:6f7c |
DDoS composite score 22.5 (challenge tier) - 239 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:50f4:e5e0:c0c3:7b60:ded4:67b8 |
DDoS composite score 25.5 (challenge tier) - 110 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6394:4e6d:641c:448b:ada5:67ac |
DDoS composite score 29.4 (challenge tier) - 236 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.122.147.229 |
DDoS composite score 32.0 (proxy tier) - 81 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.155.195.141 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 185.191.171.15 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.66.128.65 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 82.156.34.74 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.245.234.73 |
DDoS composite score 34.0 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.225.113.184 |
DDoS composite score 18.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 23.27.145.111 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a13:9500:16b:4fa0::1 |
DDoS composite score 16.3 (challenge tier) - 17 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2401:d800:942:f26e:740b:f6ff:feb5:cc98 |
DDoS composite score 15.4 (challenge tier) - 28 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.224.212.93 |
DDoS composite score 25.5 (challenge tier) - 77 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.154.98.101 |
DDoS composite score 16.3 (challenge tier) - 41 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.181.41.220 |
DDoS composite score 25.5 (challenge tier) - 116 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.113.82.5 |
DDoS composite score 22.5 (challenge tier) - 162 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a02:4780:2d:c2a5::1 |
DDoS composite score 16.3 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇭🇰 2a09:bac5:3988:2e1e::498:5f |
DDoS composite score 35.9 (proxy tier) - 140 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.244.13 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 217.216.109.88 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 151.244.197.235 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 160.225.164.132 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a04:c300:400::9c |
DDoS composite score 19.6 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.145.191.94 |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack |