User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇨🇳 129.204.188.64 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 191.237.255.150 |
DDoS composite score 38.9 (proxy tier) - 299 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 194.164.192.228 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇱🇦 202.136.244.75 |
DDoS composite score 46.7 (proxy tier) - 87 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2405:4802:801b:6df0:d191:7702:8e32:bbdc |
DDoS composite score 33.3 (proxy tier) - 168 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 3.90.235.192 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 23.27.145.21 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇦🇺 31.14.236.190 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.24.227.75 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.153.159.139 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 85.208.96.202 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 91.148.245.81 |
DDoS composite score 16.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 151.246.209.250 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 178.16.54.137 |
DDoS composite score 16.3 (challenge tier) - 30 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 2001:bc8:701:4f:da5e:d3ff:fe43:f99a |
DDoS composite score 16.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 162.216.148.0 |
DDoS composite score 15.0 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.235.80.100 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 68.178.160.25 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.178 |
DDoS composite score 23.2 (challenge tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇮 102.220.160.153 |
DDoS composite score 16.3 (challenge tier) - 24 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇩 103.187.94.254 |
DDoS composite score 23.2 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 119.13.239.187 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 143.244.57.84 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 151.246.220.18 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 205.169.39.18 |
DDoS composite score 21.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack |