User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇳🇱 45.154.98.108 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 116.110.90.18 |
DDoS composite score 25.5 (challenge tier) - 74 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 143.244.57.120 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 169.150.201.9 |
DDoS composite score 16.3 (challenge tier) - 20 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 192.145.212.232 |
DDoS composite score 40.8 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.212.5 |
DDoS composite score 38.9 (proxy tier) - 285 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 113.185.42.167 |
DDoS composite score 25.5 (challenge tier) - 78 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2401:d800:f4d:f397:3d91:2b7f:313d:57b4 |
DDoS composite score 25.5 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 5.182.207.193 |
DDoS composite score 16.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.78.203 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 43.165.197.116 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 64.89.162.167 |
DDoS composite score 16.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 81.171.72.93 |
DDoS composite score 41.8 (proxy tier) - 65 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 91.192.10.101 |
DDoS composite score 20.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 103.4.251.157 |
DDoS composite score 23.9 (challenge tier) - 95 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 147.185.132.240 |
DDoS composite score 22.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 171.217.24.55 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 198.55.112.58 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇼 198.235.24.71 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 205.169.39.49 |
DDoS composite score 21.2 (challenge tier) - 43 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 205.210.31.142 |
DDoS composite score 38.9 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 206.217.128.196 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 2401:4900:87f8:acc2:a0db:aea1:14f7:8907 |
DDoS composite score 19.6 (challenge tier) - 11 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.191.149.197 |
DDoS composite score 29.4 (challenge tier) - 171 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.135.148.92 |
DDoS composite score 38.9 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack |