User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇺🇸 43.166.134.47 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 91.92.42.120 |
DDoS composite score 19.0 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 199.47.82.21 |
DDoS composite score 16.3 (challenge tier) - 45 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:50e6:4d30:c145:3e68:7772:4e9f |
DDoS composite score 18.6 (challenge tier) - 147 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 14.191.81.74 |
DDoS composite score 29.1 (challenge tier) - 103 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:4181:25ff:49db:6aa7:c03d:f93f |
DDoS composite score 25.5 (challenge tier) - 65 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇹🇷 94.154.43.179 |
DDoS composite score 23.2 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:6379:50a9:b57a:c4a4:e56f:6012 |
DDoS composite score 29.4 (challenge tier) - 55 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2402:800:63e0:de53:1d23:3597:b845:6f0b |
DDoS composite score 20.3 (challenge tier) - 27 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:5624:c090:c5fa:2047:270d:a78f |
DDoS composite score 25.5 (challenge tier) - 86 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.174.69 |
DDoS composite score 19.6 (challenge tier) - 12 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 45.40.61.199 |
DDoS composite score 23.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇮🇳 49.156.79.53 |
DDoS composite score 19.6 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 78.142.18.172 |
DDoS composite score 19.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 113.177.217.30 |
DDoS composite score 25.5 (challenge tier) - 62 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 20.125.96.254 |
DDoS composite score 43.8 (proxy tier) - 158 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 45.154.98.26 |
DDoS composite score 16.3 (challenge tier) - 21 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇺 85.142.100.82 |
DDoS composite score 48.0 (proxy tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇸🇬 97.74.93.24 |
DDoS composite score 19.3 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 3.235.40.118 |
DDoS composite score 23.9 (challenge tier) - 54 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇨🇦 20.220.205.140 |
DDoS composite score 19.0 (challenge tier) - 69 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.139.177 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.135.145.117 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.54.138 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.119.119 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack |