User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 49.51.253.83 |
DDoS composite score 38.9 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 51.68.111.245 |
DDoS composite score 16.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.227.177 |
DDoS composite score 25.5 (challenge tier) - 53 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.35 |
DDoS composite score 29.4 (challenge tier) - 386 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.241.55 |
DDoS composite score 29.4 (challenge tier) - 244 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 85.208.96.209 |
DDoS composite score 19.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇪 85.225.108.198 |
DDoS composite score 19.6 (challenge tier) - 28 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 150.109.230.210 |
DDoS composite score 29.1 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.180.153 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 188.241.133.109 |
DDoS composite score 16.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 198.11.177.243 |
DDoS composite score 29.1 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a04:c300:400::9f |
DDoS composite score 16.3 (challenge tier) - 18 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:d741:2b0:c1f6:1206:6c83:8f7d |
DDoS composite score 29.4 (challenge tier) - 164 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.117.104.218 |
DDoS composite score 25.5 (challenge tier) - 74 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.34.103.195 |
DDoS composite score 21.2 (challenge tier) - 30 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.45.48.109 |
DDoS composite score 35.9 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.131.26.226 |
DDoS composite score 34.0 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.133.220.37 |
DDoS composite score 29.1 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.157.38.228 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.147.3 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.158.178 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.179.227 |
DDoS composite score 22.5 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.191.20 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.159.135.203 |
DDoS composite score 22.5 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.164.194.198 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack |