User hirosume2 joined AbuseIPDB in February 2026 and has reported 15,695 IP addresses.
Standing (weight) is good.
INACTIVE USER
| IP | Date | Comment | Categories |
|---|---|---|---|
| 🇩🇪 144.76.32.236 |
DDoS composite score 16.3 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 147.185.132.109 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 151.245.232.40 |
DDoS composite score 21.2 (challenge tier) - 8 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 170.106.192.208 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇵🇱 195.3.220.7 |
DDoS composite score 16.3 (challenge tier) - 10 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇪 198.235.24.196 |
DDoS composite score 22.5 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 205.169.39.52 |
DDoS composite score 23.9 (challenge tier) - 63 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇷🇴 2a02:2f0e:fc04:4000:604c:40a3:8728:687c |
DDoS composite score 35.9 (proxy tier) - 13 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇭🇰 2a09:bac5:3988:2e1e::498:5f |
DDoS composite score 35.9 (proxy tier) - 250 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 2a09:bac5:952f:3af::5e:6f |
DDoS composite score 16.3 (challenge tier) - 15 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:475c:6260:e146:411d:f0c7:1bc6 |
DDoS composite score 18.6 (challenge tier) - 138 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇻🇳 2001:ee0:5305:5fe0:5cf6:d6e1:32b0:a3f3 |
DDoS composite score 25.5 (challenge tier) - 97 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 8.231.42.104 |
DDoS composite score 16.3 (challenge tier) - 40 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇳🇱 34.12.21.212 |
DDoS composite score 39.2 (proxy tier) - 93 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 34.122.147.229 |
DDoS composite score 21.2 (challenge tier) - 42 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 35.88.190.199 |
DDoS composite score 46.7 (proxy tier) - 52 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.102.223 |
DDoS composite score 29.1 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.130.131.18 |
DDoS composite score 29.1 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇯🇵 43.130.228.73 |
DDoS composite score 22.5 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.135.130.202 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.35.128 |
DDoS composite score 19.6 (challenge tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇺🇸 43.153.49.151 |
DDoS composite score 34.0 (proxy tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇰🇷 43.155.162.41 |
DDoS composite score 18.3 (challenge tier) - 7 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇧🇷 43.157.153.236 |
DDoS composite score 34.0 (proxy tier) - 6 reqs/5min - high_traffic
|
DDoS Attack | |
| 🇩🇪 43.158.91.71 |
DDoS composite score 34.0 (proxy tier) - 8 reqs/5min - high_traffic
|
DDoS Attack |