User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
ACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 34.125.230.24 |
DDoS composite score 16.3 (challenge tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 74.7.242.39 |
DDoS composite score 25.5 (challenge tier) - 57 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 117.3.248.30 |
DDoS composite score 29.4 (challenge tier) - 203 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 118.69.66.135 |
DDoS composite score 25.5 (challenge tier) - 68 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 1.52.117.170 |
DDoS composite score 18.6 (challenge tier) - 123 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 136.66.223.197 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 202.51.202.242 |
DDoS composite score 19.3 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 49.51.183.75 |
DDoS composite score 19.6 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.75.168.164 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.183 |
DDoS composite score 23.2 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.197.43.18 |
DDoS composite score 27.1 (challenge tier) - 59 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.180.255.192 |
DDoS composite score 29.1 (challenge tier) - 110 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 42.114.2.250 |
DDoS composite score 18.6 (challenge tier) - 120 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇬🇧 213.171.208.62 |
DDoS composite score 19.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 106.52.49.148 |
DDoS composite score 29.1 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 94.176.53.196 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.235.81.195 |
DDoS composite score 26.1 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇴 176.241.66.87 |
DDoS composite score 35.9 (proxy tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 3.90.200.227 |
DDoS composite score 19.6 (challenge tier) - 9 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 193.148.56.134 |
DDoS composite score 16.3 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 5.255.124.164 |
DDoS composite score 16.3 (challenge tier) - 16 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.214.4.68 |
DDoS composite score 16.3 (challenge tier) - 19 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.85.182.98 |
DDoS composite score 16.3 (challenge tier) - 20 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 203.159.90.217 |
DDoS composite score 21.2 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 103.249.22.173 |
DDoS composite score 33.3 (proxy tier) - 55 reqs/5min - high_traffic
|
DDoS Attack |