User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 64.233.172.74 |
DDoS composite score 57.5 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 117.174.199.108 |
DDoS composite score 43.8 (challenge tier) - 88 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.247.18.43 |
DDoS composite score 34.6 (challenge tier) - 39 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.167.144.19 |
DDoS composite score 34.6 (challenge tier) - 4 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 2001:41d0:303:8670::1 |
DDoS composite score 43.8 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇪 5.62.21.135 |
DDoS composite score 43.8 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 216.73.216.155 |
DDoS composite score 34.6 (challenge tier) - 20 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 198.46.163.142 |
DDoS composite score 34.6 (challenge tier) - 26 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.174 |
DDoS composite score 32.4 (challenge tier) - 56 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 32.192.252.248 |
DDoS composite score 34.6 (challenge tier) - 47 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇦 95.177.163.4 |
DDoS composite score 43.8 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 20.63.209.197 |
DDoS composite score 43.8 (challenge tier) - 94 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.77.167.6 |
DDoS composite score 34.6 (challenge tier) - 5 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 20.200.222.0 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 116.108.0.80 |
DDoS composite score 36.9 (challenge tier) - 125 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 72.63.109.162 |
DDoS composite score 34.6 (challenge tier) - 5 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 185.171.99.203 |
DDoS composite score 34.6 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 91.98.185.79 |
DDoS composite score 31.7 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 95.164.129.240 |
DDoS composite score 37.9 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.77 |
DDoS composite score 57.5 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:61af:f54a:750c:5e1a:6e59:dd43 |
DDoS composite score 38.6 (challenge tier) - 135 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇴 20.100.169.43 |
DDoS composite score 37.3 (challenge tier) - 98 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇹 62.60.130.224 |
DDoS composite score 34.6 (challenge tier) - 35 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.117.214.192 |
DDoS composite score 43.8 (challenge tier) - 74 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.67 |
DDoS composite score 57.5 (challenge tier) - 52 reqs/5min - high_traffic
|
DDoS Attack |