User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇮🇳 20.219.23.189 |
DDoS composite score 37.9 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 2404:7a80:2980:c200:79c1:5677:a601:de9c |
DDoS composite score 37.9 (challenge tier) - 36 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 172.115.71.11 |
DDoS composite score 43.8 (challenge tier) - 60 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇳 113.31.186.146 |
DDoS composite score 37.9 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 168.144.40.70 |
DDoS composite score 34.6 (challenge tier) - 37 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇪 20.238.112.20 |
DDoS composite score 48.7 (challenge tier) - 342 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 4.211.248.24 |
DDoS composite score 37.9 (challenge tier) - 50 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 118.70.81.130 |
DDoS composite score 36.9 (challenge tier) - 105 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 44.222.163.66 |
DDoS composite score 43.8 (challenge tier) - 128 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 54.211.132.46 |
DDoS composite score 43.8 (challenge tier) - 91 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇫🇷 185.177.72.17 |
DDoS composite score 34.6 (challenge tier) - 32 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.173.240.198 |
DDoS composite score 34.6 (challenge tier) - 85 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 64.227.64.251 |
DDoS composite score 31.7 (challenge tier) - 201 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 64.233.172.77 |
DDoS composite score 57.5 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 100.54.194.146 |
DDoS composite score 43.8 (challenge tier) - 129 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.151.105.117 |
DDoS composite score 34.6 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 52.205.48.46 |
DDoS composite score 43.8 (challenge tier) - 68 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 164.92.208.250 |
DDoS composite score 36.9 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.153.208.26 |
DDoS composite score 43.8 (challenge tier) - 64 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇩 157.66.55.50 |
DDoS composite score 44.8 (challenge tier) - 101 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇹 4.232.179.255 |
DDoS composite score 34.6 (challenge tier) - 33 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 66.249.89.39 |
DDoS composite score 43.8 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 40.77.167.154 |
DDoS composite score 34.6 (challenge tier) - 5 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 132.196.61.110 |
DDoS composite score 48.0 (challenge tier) - 228 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.148.10.120 |
DDoS composite score 32.4 (challenge tier) - 90 reqs/5min - high_traffic
|
DDoS Attack |